Heikki Toivonen wrote:
Markku Mielityinen wrote:
1) The generated pot file contains a lot of duplicate entries which
unnecessarily take time when translating and they also prevent the use
of GNU gettext tool package.

2) There are some duplicate entries due to differences in letter
capitalization. At some point we might want to consider unifying these
entries.

Are you absolutely sure they are real duplication? My first reaction was
that yes, there are multiple instances of a word, but in different
contexts. In other languages that same word might need to be several
different words depending on context.

Also, capitalization often depends on context.

Your point is valid but I am still convinced that there are instances of duplicate entries.

3) There are still strings in source code that should be translated,
i.e. wrapped inside _(). For example displayName and startTime in the
header and Test menu, which we on the other hand might not want to
translate for other reasons.

4) There are strings that are currently wrapped inside _() when they
should not be. The correct way to enter non-translated  strings is to
use _T() wrapper. For example ":", ":." etc.

File a bug and make a patch :)

Yup.

5) Accelerated keys are currently wrapped in _() blocks. Whereas the
accelerated keys are typically localized, it is currently hard for the
translator to localize these in a consistent manner. Hence, we might
want to reconsider if localizing then, at least at this point, is a good
idea.

I would leave them as is. The localizers do not need to localize them,
but they can if they want to.

I agree that this is the correct approach to take now. I just wanted to point out the difficulties in localizing accelerated keys.

6) There is some inconsistency in the way Show/Hide vs Hide/Show is
used. Perhaps we should choose one, Show/Hide, and use this order in all
places.

Depends on context again. But definitely worth thinking about. Could you
list all the specific locations where these happen?

These are very easy to find directly from the GUI or from a generated pot file.

7) There is still some polishing to do: fixing typos and improving the
structure of some sentences. But hey, who is counting at this point...

Patches, patches :)

In addition Philippe noticed that:

8) Building "MyTasks", "My..." by catenation of "My" and "..." does not
work for many locales.

File a bug for these exact locations please.

I will do that and also provide a patch as well :)


Also an item from Philippe's email raised a red flag:

9) Some strings are written into the repository, meaning that these
strings are not translated if you change the locale after they were
written to the repository. We should file bugs for these instances as well.

This is a valid issue that was considered when Brian, PJE, John, and I planned how to implement the translation service. Correct me if I am wrong but I think that the consensus was that it is unlikely that the user would like to change the locale setting very often. Hence, it was decided that either we would provide a mechanism to rebuild the GUI in repository or we would require the user to do --create when changing the locale setting.

Cheers,
   Markku
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to