|
|
|
Forum Newbie
Group: Forum Members
Last Login: 8/17/2005 10:23:14 PM
GenoPro Version: 1.99
Posts: 2,
Visits: 0
|
|
| Go would do, to language configuration attempt life to the some external set e.g . language.ini ??? It would be good for program translation to the other language thereby facilitation diffusion programme... Thank you behind well - considered that improvement.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 10:15:34 AM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,174
|
|
Translating with a resource editor is a one-shot deal. Putting everything into an .ini file does not solve the problem of translating the dialogs and the menus, not even the string tables. How do I make sure every string and every expression has been translated. What about when I add a new dialog, how do I make sure it has been translated in the .ini file... in every language. This is not an easy problem to solve.
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: 8/17/2005 10:23:14 PM
GenoPro Version: 1.99
Posts: 2,
Visits: 0
|
|
| At translating programme is much simpler, when translates programme only in *.ini. When the will give up new version, so doesn't need to translate again everything from again, but be enough translate only a few new added text chains etc .
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 10:15:34 AM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,174
|
|
| You are not answering the question of my last post. You are telling me the benefits of a .ini file. How do I move the text from the dialogs, the menus, and string tables to the .ini file? The resource compiler has no clue of a .ini file and I have no plan to write my own resource editor and resource compiler. I know I could do something like this in C++, by enumerating each control and matching the ID with a string in the .ini file. There are problems with this however:
Some of the text is formatted (interactive), so a straight assignment cannot work. One solution would be to remove the formatted text, however it would make it harder for the user to use GenoPro.
In some languages the text is longer than English. As a result, some controls would have to be stretched, or moved somewhere in the dialog.
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: 8/17/2005 10:43:21 PM
Posts: 6,
Visits: 0
|
|
1. Some of the text is formatted (interactive), so a straight assignment cannot work. One solution would be to remove the formatted text, however it would make it harder for the user to use GenoPro.
no sweat. let pass this problem.
2. In some languages the text is longer than English. As a result, some controls would have to be stretched, or moved somewhere in the dialog.
MicroSoft is advise:
user can set big font.
user can set bad color.
user can ...
...
You must be ready for it.
AutoSize=true;
big free space...
and this problem is problem translators.
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 2 days ago @ 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
You forgot all the treatment in the RTL languages.
In Hebrew you will have to add the ability to translate from English to Hebrew AND reverse the direction to RTL.
so you will have to add:
RTL=true
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 10:15:34 AM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,174
|
|
I am thinking of using an XML file to store all the strings for a specific language, similar as Dictionary.xml from the report generator. The XML file could also contain additional information to resize and move controls within the dialog layout.
Example of a french translation of the Cancel button:
<control id="2" text="Annuler" width="80" />
|
Each time a dialog would see the control ID 2 (the Cancel button), it would substitute the text with "Annuler" and set the width to 80.
If for instance, a specific dialog needs a different text for the Cancel button (such as Abort), the XML file would be the following:
| <dialog id="123"><control id="2" text="Arrêt"/></dialog> |
One advantage of the XML is it has built-in Unicode, and an option could be RTL (Right-to-Left).
Here are the attributes I am looking to include:
id = identification of the control. Each control in a dialog has a unique ID, and each ID would become "public" so everyone can know what ID is associated with each control. Of course, an experienced computer user can use a resource editor to "reverse engineer" the IDs, so there is no real *need* for GenoPro to publish the IDs.
text = text for the control. This text could also contain the keyboard accelerator, such as "&Annuler" to enable the Alt+A shortcut.
width, height = change the width and/or height of the control. If the text is too long to fit in the original layout, the width of the control could be re-sized. The value would be likely be in "Dialog Units", however pixels may also be supported. One feature I am considering is to support + and - to specify by how much to change the width and/or height.
xPos, yPos = change the position of the control. Again, the coordinate could be in dialog units, or pixels. Using the + or - would shift the control by a given delta rather than specifying the position.
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: 8/17/2005 10:43:21 PM
Posts: 6,
Visits: 0
|
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 10:15:34 AM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,174
|
|
After the release of version 2.0. I will do translation in French (my mother tongue) as a test drive, and then make the IDs public.
|
|
|
|
|
Junior Member
Group: Customers
Last Login: 9/6/2009 3:34:07 PM
Posts: 21,
Visits: 154
|
|
In my programs (Visual Basic) I use system of tags, so every field in dialog has unique number. Of course, I use the same number for the same text like Ok or Cancel, and larger increment than 1 for upgrade purpose. I use this method for ToolTipText and with small modifications for menu (caption=number) and toolbar buttons.
During loading of dialog, custom procedure replaces all these numbers by proper text, which is stored in .ini file, and changes font charset, which is specified in .ini file too (0=Western, 204=Cyrilic, ...). In dialogs I must use TrueType font (Tahoma), of course. But some text is shown still incorectly if system language differs from specified one (menu items).
Internationalization isn't posible without good design of dialogs. I use more "white space", controls are positioned below caption (not beside) and so on. By my view, specification of width, height and top left corner of fields is more complicated way.
Something about design user interfaces (note very concrete):
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon98/html/vbconthebasicsofinterfacedesign.asp
Many internationalization resources can be found at:
http://www.i18ngurus.com/docs/984813521.html
|
|
|
|
|
Forum Guru
Group: Customers
Last Login: 11/3/2009 7:43:48 AM
GenoPro Version: 2.0.1.5
Posts: 154,
Visits: 637
|
|
GenoProSupport (8/18/2005)
After the release of version 2.0. I will do translation in French (my mother tongue) as a test drive, and then make the IDs public.It's not possible to start with the translation before? I know it's a lot of work and we can do a lot of work if we have the IDs.... than, after the 2.0 is only a rest to do.... (I want to work with the Catalan and Spanish languages) 
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 10:15:34 AM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,174
|
|
Jordi-Albert Batalla
It's not possible to start with the translation before?The current structure of GenoPro is not capable to substitute translated text from the XML file descriging the language. I need to write the code to substitute text for menus, dialogs, buttons, error messages and more.
|
|
|
|
|
Forum Guru
Group: Customers
Last Login: 11/3/2009 7:43:48 AM
GenoPro Version: 2.0.1.5
Posts: 154,
Visits: 637
|
|
| But a lot of people can starting with the translation. We must have only the XML file with all the text to translate.....because we need a lot of time for this work.... If I can't starting with the translation all the people that want genopro in another language must wait for uns...
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 10:15:34 AM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,174
|
|
Jordi-Albert Batalla (8/30/2005)
We must have only the XML file with all the text to translate.....because we need a lot of time for this work....I agree, but the XML file format for the translation has not been designed yet. This XML file will have many sections, including text fallback, and chaining of translation dictionaries. I also need to write the code to read the XML file and substitute the translated text to the menus and dialog. One of the problem is GenoPro uses MFC compiled without Unicode, so there is extra work. The translation is important to me... I am thinking about it everyday.
|
|
|
|
|
Forum Guru
Group: Customers
Last Login: 11/3/2009 7:43:48 AM
GenoPro Version: 2.0.1.5
Posts: 154,
Visits: 637
|
|
| Thanks. we wait and we know that is a lot to do before the 2.0, so... no problem
|
|