In my last post, one sentence got cut. What I'm "waiting for" is
someone to tell me they are compiling Chromium at home, knows the
translation tools and could take my changes and give me back a DLL!
I just read up on gettext. Lookups are done using a table with
original strings and hashes, and the localized string at the end. The
obvious waste is that the original strings are stored once in the
executable, and once in each compiled translation file.
This issue already bit me: Sometimes a word ("file"
http://en.wiktionary.org/wiki/file
) needs different translations depending on usage. Then straight hash-
lookup won't do it.
Maybe this problem has been solved in Googles own translation system?
Together with the double storage, possibly faster lookup and native
efficient(?) DLL-caching, this might be the reason G. didn't stay with
gettext.
(Another thing. Gettext "handles hash collisions with double hashing".
Chromiums translations use a MD5 hash -- is there a check in place to
discover hash collisions?)
> On 21 Sep., 21:37, "Simon B." <[EMAIL PROTECTED]> wrote:
>
> > For translators it can be very useful to have the translations file as
> > a separate data file. As it is now, I have prepared some half-hearted
> > translation attempt and waiting for [...]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
