Posted by: David
« on: July 18, 2006, 07:11:31 PM »Thanks again! Version 1.2 Preview 7 has your changes.
Posted by: Rheuh
« on: July 18, 2006, 09:17:45 AM »And here is the translation.
Posted by: David
« on: July 18, 2006, 07:24:00 AM »Another update for 1.2 Preview 6 attached.
Posted by: David
« on: July 17, 2006, 09:03:06 AM »I don't know how I missed your post about writing translation tools. That would be fantastic! Sorry I didn't see your message in time for your holiday. I'll split your post into a separate topic.
Posted by: David
« on: July 17, 2006, 09:01:15 AM »I've attached the French translation modified for version 1.2. I marked the new items that need to be translated with "TODO" in the comment tag.
Posted by: David
« on: June 21, 2006, 05:14:16 PM »I updated the cab file with the new strings. Thanks!
"Éclairage permanent dans le jeu" would not fit. I also tried "Rétro-éclairage permanent", which did not fit.
So I cut it down to simply "Éclairage permanent".
I'll make this dialog scroll (or free up more space) at some point, but I hope this will be sufficient for now.
RE: the MUI interface, this is essentially what I'm doing, except in the .NET Compact Framework, you use the culture names instead of the lcid. So, "en-US" instead of "0409".
If you open the dll installed by the cab in Visual Studio, you can edit the resources there. Also, Visual Studio can open the resx file.
But what I really need is for new strings and changes from the neutral English version of the resources to be flagged for translation and merged into the other language files. As far as I know, Visual Studio does not do this.
"Éclairage permanent dans le jeu" would not fit. I also tried "Rétro-éclairage permanent", which did not fit.
So I cut it down to simply "Éclairage permanent".
I'll make this dialog scroll (or free up more space) at some point, but I hope this will be sufficient for now.
RE: the MUI interface, this is essentially what I'm doing, except in the .NET Compact Framework, you use the culture names instead of the lcid. So, "en-US" instead of "0409".
If you open the dll installed by the cab in Visual Studio, you can edit the resources there. Also, Visual Studio can open the resx file.
But what I really need is for new strings and changes from the neutral English version of the resources to be flagged for translation and merged into the other language files. As far as I know, Visual Studio does not do this.
Posted by: Rheuh
« on: June 21, 2006, 11:15:10 AM »Whooops... here it is, the good one.
For the MUI interface, just take a look at the \windows directory on any smartphone. There you'll find dlls and exes which native language is American English, and say that you take something.dll, you'll also find something.dll.040C.mui for the French translation, something.dll.0410.mui for Italian (not sure), etc... I have no idea how all of this is implemented, all I know is that when you open .mui files in Restorator or VS Resource editor on the computer, you can modify the strings and the bitmaps. So it must be some kind of resource-only DLL.
(BTW, MUI stands for Multilingual User Interface, apparently it's also used on Tablet PCs and will be used in Vista, too).
Concerning the website, I'll be translating it as soon as I got some time. I'll upload it there ASAP.
For the MUI interface, just take a look at the \windows directory on any smartphone. There you'll find dlls and exes which native language is American English, and say that you take something.dll, you'll also find something.dll.040C.mui for the French translation, something.dll.0410.mui for Italian (not sure), etc... I have no idea how all of this is implemented, all I know is that when you open .mui files in Restorator or VS Resource editor on the computer, you can modify the strings and the bitmaps. So it must be some kind of resource-only DLL.
(BTW, MUI stands for Multilingual User Interface, apparently it's also used on Tablet PCs and will be used in Vista, too).
Concerning the website, I'll be translating it as soon as I got some time. I'll upload it there ASAP.
Posted by: David
« on: June 21, 2006, 06:37:46 AM »Rheuh, it looks like you must have uploaded the wrong resx file. The file you attached is the same as the old one and doesn't contain the new strings.
Posted by: David
« on: June 20, 2006, 11:46:07 PM »Thanks! I'll update the lang pack tonight.
What MUI interface are you referring to? I'm not familiar with it.
And yes! A French version of the pages would be great!
What MUI interface are you referring to? I'm not familiar with it.
And yes! A French version of the pages would be great!
Posted by: Rheuh
« on: June 20, 2006, 06:26:27 PM »Here comes the new .fr.resx.
By the way, why don't you use the MUI interface provided by Windows Mobile for translations ?
Edit : if you want a French version of the page located at http://www.smoresoft.com/sudoku/, please just let me know, it's no problem for me. That would perhaps help to better spread your game (and as I said, I could advise it to my French customers).
By the way, why don't you use the MUI interface provided by Windows Mobile for translations ?
Edit : if you want a French version of the page located at http://www.smoresoft.com/sudoku/, please just let me know, it's no problem for me. That would perhaps help to better spread your game (and as I said, I could advise it to my French customers).
Posted by: David
« on: June 20, 2006, 06:10:00 PM »I updated the Resources.resx file attached to the Translating Smoresoft Sudoku topic.
Sorry, I know this is not a very efficient way to handle incremental changes. I'll come up with something better when I get the time.
Sorry, I know this is not a very efficient way to handle incremental changes. I'll come up with something better when I get the time.
Posted by: Rheuh
« on: June 19, 2006, 09:15:16 PM »In "power management", backlight is translated "rétro-écl." which is in fact short for "rétro-éclairage".
For my part, I prefer the single word "éclairage". Do you *really* think people will confuse backlight with the ambient light in their room ?
So if you choose the short translation (I agree that there's not many space on the screen), I think you'd better use "éclairage" rather than "rétro-écl." that non-techies may not understand. Keep it simple & stupid
For my part, I prefer the single word "éclairage". Do you *really* think people will confuse backlight with the ambient light in their room ?
So if you choose the short translation (I agree that there's not many space on the screen), I think you'd better use "éclairage" rather than "rétro-écl." that non-techies may not understand. Keep it simple & stupid
Posted by: David
« on: June 19, 2006, 08:44:18 PM »When you go to "Start", "Settings", "Power Management" on your phone, how is the word "backlight" translated there? I think I would like to use the same thing, so you can correlate it with the Windows Mobile setting.
I do have very limited space in the Options dialog at the moment since it does not support scrolling yet. So I'll probably have to take a short translation for now. When I get around to making it scroll, I can make it longer.
I do have very limited space in the Options dialog at the moment since it does not support scrolling yet. So I'll probably have to take a short translation for now. When I get around to making it scroll, I can make it longer.
Posted by: Neverwish
« on: June 19, 2006, 04:22:51 PM »Yes it is, because when the option is checked, backlight stops when the game is not on screen whereas it does not when it is on screen.
Furthermore, Backlight means Rétro-éclairage, instead of Eclairage.
Furthermore, Backlight means Rétro-éclairage, instead of Eclairage.
Posted by: Rheuh
« on: June 19, 2006, 04:04:10 PM »Do you really think such a long title will fit on the screen ? I mean, "permanent lighting", that's perfectly understable, no ?
Perhaps "Éclairage permanent dans le jeu" -- permanent lightning when in game -- if you really think the "in-game" aspect is important. But I really believe it's not worth overloading the user with lots of text.
Perhaps "Éclairage permanent dans le jeu" -- permanent lightning when in game -- if you really think the "in-game" aspect is important. But I really believe it's not worth overloading the user with lots of text.