Dear all,
> The only thing I found was this:
> http://www.csn.ul.ie/~caolan/publink/winresdump/winresdump/doc/resfmt.txt
> and that's what I used to implement ResText.
>
THX I will have a look.
>>> And AFAIK poEdit doesn't know about groups either. So it would be
>>> difficult to make "groups" in a po file.
>> The idea was to have separate group files to this and separate tool
>> for check this. Some kind of report. Not change translations workflow
>> in any way.
>> Something like there is report in
>> http://tortoisesvn.net/translation_devel_gui, where you can find
>> missing accelerators. And every Monday you can receive similar
>> report. Maybe this may be used list of conflicted acc.keys. Maybe
>> there may be another page in let say
>> http://tortoisesvn.net/translation_devel_gui_errors.
>
> One problem: if in the default (English) language are two identical
> strings (e.g. &Copy), you will only see one such string in the po
> file. But in another language, you might want to set the accelerator
> for one of those strings differently than for the other, because they
> are used in different menus/dialogs/...
> How would you handle this situation? The only real solution to that
> would be to not pack identical strings together - much more work for
> the translators.
Ok.
Keep in mind:
1. No change in translation work(flow).
2. Only report for bad (overlaping) keys.
3. Grouping files are separated list of texts in same menu.
As think about this when this idea comes I found that if any string
(lets use you example) &Copy (SK: &KopÃrovaÅ¥) is used in more "groups"
it will apear in all this groups, but only once in .po as today. So
there may be only one translation of &Copy, but when you overlap key in
any group you will know it, because you get any report about.
Alternatively you (as translator) can manually go thru groups and select
proper acc.keys (or none). As now you get report (notification) you miss
translate any acc. key by site check or Monday email you will get info
about that you overlap some.
If I can tell what we need to do in order to get this result.
1. Make group files. This looks to as hardest job. Find way how to
collect all menu items which apear in same menu.
We can store it in plain text files or in one with some separator. Let
say "-------" as separator of group. Every menu item in separate line.
This will get oportunity to check acc.key myself as now I don't know in
how many and which menus &Copy (SK: &KopÃrovaÅ¥) appear, but I should not
to use &K in any other menu item in such group.
2. Make some tool to extract used acc. key for every group in
translation from .po file and make report about confilcts. Let say .php
scipt, which will generate such report when translation status is generated.
Oto
PS: I can accept 'NO', but I don't like. :)
--
Oto BREZINA
SW R&D Manager
Printflow, Slovakia EU
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Sep 14 22:24:36 2007