I have modified the en-US .po file (changing keyboard shortcuts), used poEdit to create a .mo file and the mere appearance of that .mo file in the en-us folder provided me with access to the changes I had made.
As you know, Gerald, I'm working with translating XMLCE into Khmer.
Since I'm not using Khmer localization, how would I go about seeing how things work so far? (I've translated 155 of the 404 messages in the .po file.)
If I made a km folder and a messages.mo file for it, how would I access that?
And if I actually put that khmer messages.mo file in us-en, would that work at all?
Thanks for your help on this. Probably I should go read up more on what native Khmer users need to do to make this work in their systems. :-)
Roger Sperberg
38 percent completed with the Khmer XMLCE
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Roger, that's exactly what you could do: if you drop your messages.mo into the en-us folder, you can test-drive your translation. You could also replace one of the existing translation files (German, French, Slovak, Swedish, Chinese) so you can still switch back to the original version for comparisons just by switching languages in Tools>Options.
If anything isn't working as expected, let me know!
-Gerald
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
PS Creating a km folder will not work at the moment - to ensure users can switch between all localisations in Tools>Options I'm activating translations explicitly in the source at the moment.
-Gerald
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've just downloaded XML CopyEditor ver. 1.1.0.3 and found it quite good.
I want to localize it in Italian language but messages.po, stored in 'it' folder cannot be accessed.
Is that functionality to be still implemented?
In any case, as soon as I shall be able to test my translation I shall send you the file .po
Bye
--
Antonio A.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"I'm activating translations explicitly in the source"
Ah, I figured that when I saw the drop-down list.
I did try putting it in en_us and it did work (except for one thing). I think I'll put it in Chinese instead, so I can switch back and forth as you suggest.
For some reason, I'm unable to control the font used in dialog boxes in Win XP. I think it's Microsoft Sans Serif 8 pt. At any rate, that font doesn't contain Khmer characters and so rectangle blanks show up instead of the text in, say, the Options dialog box. All the other font controls are changed in Control Panels -> Display -> Appearance tab [Select Windows Classic style] -> Advanced button [change all font instances, eg Menu, Active Title Bar, etc. to a Khmer font such as KhmerOS System].
Vista probably doesn't have this issue. Since I haven't read about other people having the same problem in XP -- and it's a show-stopper -- I'm exploring several approaches to fixing this.
What does seem to be a bug (wrong forum), is that the menu names in XML CE are displayed in this font instead of in the same font as the menu commands -- both of which are controlled by the 'Menu' item in the Advanced button mentioned above. But that problem is not specific to Khmer; it was that way before I tried this.
I'll advise you if I'm able to resolve these issues.
Roger
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just to let you know that I put the messages.mo file with 155 Khmer terms (and the rest left blank, so they're picked up from en, right?) into the sk folder (renaming the original). I was able to choose it from within XMLCE and switch back and forth between en-us and the khmer/english version identified as Slovak.
That enables me to check the Khmer as I go, so I thank you for your assistance here.
For the record, I tried doing this first with Traditional Chinese, but I received an error message saying that XMLCE was unable to use the Chinese format. Probably something about localization and such, I guess. Win XP, of course.
Also for the record, this doesn't work unless the Advanced settings button in the Appearance tab of the Display Control panel is set to use a font that contains Khmer characters.
Roger
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Antonio, that's great! The easiest way to test a new translation is to drop your compiled messages.mo into en_US. (Are you using poEdit or msgfmt to edit the file? Roger has also set up a launchpad entry for the project so you might be able to use that for the translation.)
Alternatively you could send me the po file and I'll put it in for 1.1.0.4!
Cheers,
Gerald
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have modified the en-US .po file (changing keyboard shortcuts), used poEdit to create a .mo file and the mere appearance of that .mo file in the en-us folder provided me with access to the changes I had made.
As you know, Gerald, I'm working with translating XMLCE into Khmer.
Since I'm not using Khmer localization, how would I go about seeing how things work so far? (I've translated 155 of the 404 messages in the .po file.)
If I made a km folder and a messages.mo file for it, how would I access that?
And if I actually put that khmer messages.mo file in us-en, would that work at all?
Thanks for your help on this. Probably I should go read up more on what native Khmer users need to do to make this work in their systems. :-)
Roger Sperberg
38 percent completed with the Khmer XMLCE
Hi Roger, that's exactly what you could do: if you drop your messages.mo into the en-us folder, you can test-drive your translation. You could also replace one of the existing translation files (German, French, Slovak, Swedish, Chinese) so you can still switch back to the original version for comparisons just by switching languages in Tools>Options.
If anything isn't working as expected, let me know!
-Gerald
PS Creating a km folder will not work at the moment - to ensure users can switch between all localisations in Tools>Options I'm activating translations explicitly in the source at the moment.
-Gerald
Hello!
I've just downloaded XML CopyEditor ver. 1.1.0.3 and found it quite good.
I want to localize it in Italian language but messages.po, stored in 'it' folder cannot be accessed.
Is that functionality to be still implemented?
In any case, as soon as I shall be able to test my translation I shall send you the file .po
Bye
--
Antonio A.
"I'm activating translations explicitly in the source"
Ah, I figured that when I saw the drop-down list.
I did try putting it in en_us and it did work (except for one thing). I think I'll put it in Chinese instead, so I can switch back and forth as you suggest.
For some reason, I'm unable to control the font used in dialog boxes in Win XP. I think it's Microsoft Sans Serif 8 pt. At any rate, that font doesn't contain Khmer characters and so rectangle blanks show up instead of the text in, say, the Options dialog box. All the other font controls are changed in Control Panels -> Display -> Appearance tab [Select Windows Classic style] -> Advanced button [change all font instances, eg Menu, Active Title Bar, etc. to a Khmer font such as KhmerOS System].
Vista probably doesn't have this issue. Since I haven't read about other people having the same problem in XP -- and it's a show-stopper -- I'm exploring several approaches to fixing this.
What does seem to be a bug (wrong forum), is that the menu names in XML CE are displayed in this font instead of in the same font as the menu commands -- both of which are controlled by the 'Menu' item in the Advanced button mentioned above. But that problem is not specific to Khmer; it was that way before I tried this.
I'll advise you if I'm able to resolve these issues.
Roger
Just to let you know that I put the messages.mo file with 155 Khmer terms (and the rest left blank, so they're picked up from en, right?) into the sk folder (renaming the original). I was able to choose it from within XMLCE and switch back and forth between en-us and the khmer/english version identified as Slovak.
That enables me to check the Khmer as I go, so I thank you for your assistance here.
For the record, I tried doing this first with Traditional Chinese, but I received an error message saying that XMLCE was unable to use the Chinese format. Probably something about localization and such, I guess. Win XP, of course.
Also for the record, this doesn't work unless the Advanced settings button in the Appearance tab of the Display Control panel is set to use a font that contains Khmer characters.
Roger
Thanks Antonio, that's great! The easiest way to test a new translation is to drop your compiled messages.mo into en_US. (Are you using poEdit or msgfmt to edit the file? Roger has also set up a launchpad entry for the project so you might be able to use that for the translation.)
Alternatively you could send me the po file and I'll put it in for 1.1.0.4!
Cheers,
Gerald