Re: How to separate different uses of the same entry?

Hi Lübbe,

2007/6/1, Lübbe Onken <l.onken@rac.de>:

> The .po files support developer and translator comments, but the xml2po.py
> utilty must be able to create them from the source. I don't know if xml2po
> supports comment markup in xml files.

I know that, and I'm using comments for myself broadly while translating :)

> If you run "nant potfile" in the doc subdirectory, you will create the
> complete english xml file which is used for translation. Then you can use
> the context menu in poedit to jump to the source location of the string that
> you want to translate. This is what I do to check these cases and it's
> probably quicker than trying to patch xml2po.py.

I know how I could translate it, the problem is that in some cases
there is the _same_ entry for different translation cases, even for
those which doesn't need translation at all! (Recent example -
'revision', used as keyword).

The best solution would be the different entries for different use
cases. Use case will be indicated with comments in .xml source. I
think of using different word casing as a workaround, but I'll look
for more robust solution.

Stan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Jun 1 10:24:05 2007