[Etoys] Progress/Status Translation

Korakurider korakurider at gmail.com
Thu Apr 10 12:19:18 EDT 2008


On Thu, Apr 10, 2008 at 10:28 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>  >     The downloadable files you mentioned are just result of the
>  > latest build and aren't package perfectly ready for use.  Those don't
>  > contain compiled MOs, so basically you need to place MOs manually.
>  Actually, the non-dev version should be ready for use. It has MOs.
    Aha, I missed the change :-)

>  >> The etoys.image has a lang-directory, the etoys-dev.image has a
>  >> po-directory. Any chance to unifiy them.
>  >   We could have both directories in both archives :-)
>
>  Why? The one is the source, for developers, the other the compiled
>  result, for users. Shipping POs to users doesn't make sense, and
>  having POs in the dev zip would be redundant.
    I agree current packaging is space optimal.   But I also thought
that it might be confusing to translators but non-developer.

>  >> Any chance to include the latest translation-cs form ticket 6704 into
>  >> the images and Pootle:-)
>  >    This is different topic and still needs some work by developers...
>
>  I wish there was a way to flag tickets that have a patch waiting for
>  inclusion in the image ... It's too easy to forget about them. We
>  should definitely push the changesets to the update stream (though I
>  have not looked at them in detail, yet).  And make a new release
>  soonish.
    I still have some remaining work for the ticket (translate symbols
for emphasis & alignment with flattering CamelCase.  And I have come
to think that by addressing #6810, flattering symbols with CamelCase
can be handled better).
    Having bunch of small changes for so many places, it might be
risky to push the patches at this stage, but it would be nice if we
can release them soon.

/Korakurider


More information about the Etoys mailing list