j_c_hallgren wrote:DmFederov is showing the format that I've seen used in most language files that I've seen .....
Than you haven't seen language files (resource bundles) in Java (or some other languages) where you have a file per language.
IMHO, this is an much better approach. A translator can focus on his keys/labels and is not in danger of smashing existing localizations.
BTW, UltraEdit is a proper reference for good software.
-------------It is not criticism. Ok?------------
No matter what form will be selected as lng-file (when it works)
I only wish tell what I will do to translate this list.
I will load it into microsoft acces or I will load it into the Radialix program.
I will make it for the simple reason: Blindly it is almost impossible to translate for receiving a high-quality translation.
In Access I can sort, do inquiries, achieve the same examples-translation and have columns where will be specified in what place there is a line for translation.
More better effect I will receive in the Radialix translate-program. Better - because changes are traced. And you know: XY changes often.
I think that for translation nevertheless it is necessary to have a kind of a blank, (kind of preparation) with notes where there (in XY) is every line. After translation file should be overworked and brought into a look which requires a minimum for memory load. For example i can delete these notes.
------
in XY code i have not found the >>
>> is very good.
Yes, you can probably do a lot of things with Radialix. But, of course, not every possible translator has Radialix. I try to keep the LNG file format as self-explaining as possible.
And generally @all: The task here is to open an very big application like XY (DmFedorov counted 7,000 places that need translations) for Multilingual Support after 15 years of daily development hard-coded to English. This needs a little out-of-the-box thinking and non-standard solutions in order to get to good results in a reasonable time while keeping the app open and unhindered for further development in the future at the same speed as before.
I'll for sure not translate XYplorer (since I do not think that there would be any more interest for a non-English XYplorer in the speaking areas of the languages known to me) but nevertheless I am a fan of your format.
It is very similar to something I have conceptualised some years ago while developing something with Delphi (but run out of time and energy before it ever got out there in the world). Would the coding be UTF-8? In my application (the one which was dead before birth, so to speak), I was easily able to switch GUI language on the fly, without the need of closing application.
Personally, I was always wondering why that mess with resource strings and the like. So, if I were you, I would definitely go the way you are suggesting.
(But, I admit, I have BeyondCompare and would probably be using it for tracking your possible daily introduction of new strings to be translated. So, maybe it would not be a bad idea if you would conceive a system of pointing out the newly introduced strings for existing translations, in order to facilitate keeping translation in sync with your development.)
UTF-8 or Unicode. Depends on further testing, especially East-Asia.
Borut wrote:(But, I admit, I have BeyondCompare and would probably be using it for tracking your possible daily introduction of new strings to be translated. So, maybe it would not be a bad idea if you would conceive a system of pointing out the newly introduced strings for existing translations, in order to facilitate keeping translation in sync with your development.)
Just FYI: Making good progress. It's actually a fascinating job. Today I successfully completed the grammatical number algorithms for all major languages, actually for almost all languages mentioned on this page: http://unicode.org/repos/cldr-tmp/trunk ... rules.html
I skipped Manx for now, sorry Isle of Man, bump me if you need it. But, of course, my algorithms are abstract enough to also add Klingonian if needed, even Kölsch! Well, I made it even open and extensible, so YOU could add your particular dialect of Klingonian easily!