|
|
|
IT Director GenoPro
 
Group: Customers
Last Login: Yesterday @ 6:21:34 PM
GenoPro Version: 2.0.1.6
Posts: 432,
Visits: 5,645
|
|
| Yehudad, the good news is that the new skin can be almost completly translate to another language from a single file! I think that Russian, spanish and french has been done this way. I know that Hebrew is more complex because of the RTL text.
If the facts don't fit the theory, change the facts.
-- Albert Einstein Jean-Claude Morin
Information Technology Director, GenoPro.
http://www.genopro.com
|
|
|
|
|
Forum Master
 
Group: Customers
Last Login: 2 days ago @ 1:39:10 AM
GenoPro Version: 2.0.1.4
Posts: 552,
Visits: 7,227
|
|
Ron (7/19/2007)
In many cases this can now be achieved by 'merely' translating the Dictionary.xml file. It also has a number of features to allow modification of the Report again without recourse to a custom skin. I am interested to know what changes you are making to the skin for your Hebrew Report. Perhaps I can accommodate your requirements in the standard skin too. JcMorin (7/19/2007)
Yehudad, the good news is that the new skin can be almost completly translate to another language from a single file! I think that Russian, spanish and french has been done this way. I know that Hebrew is more complex because of the RTL text. I wish that it was that easy. There are some unique Hebrew grammer that I don't think a simple translation like from English to Franch or Spanish does. For example translating the dates - I can use the hebrew calander or I can translate the Gregorian one into Hebrew. This is not somthing that I can only use the dictionary.xml. I'm trying as much as I can to put the translations in the dictionary.xml but I still have phrases that are different for male and female. For instance you are using the word "is" for both, while in Hebrew I need to use Is_M, Is_F and Is_. The code should be modified as well with the individual's gender to select the right term. I guess that while translating, I will find more thngs, like the Hyperlink issue. I hope that when I will finish my work, the translation will be more automatic like the other languages.
|
|
|
|
|
Grand Master
Group: Customers
Last Login: Today @ 4:04:45 AM
GenoPro Version: 2.0.1.5
Posts: 1,029,
Visits: 4,708
|
|
Yehudad (7/19/2007)
I'm trying as much as I can to put the translations in the dictionary.xml but I still have phrases that are different for male and female. For instance you are using the word "is" for both, while in Hebrew I need to use Is_M, Is_F and Is_. The code should be modified as well with the individual's gender to select the right term. The code & Dictionary already has the capability for male/female forms of 'is' (or ToBe_Present). You can add ToBe_Present_F and/or ToBe_Present_M forms. This is (badly) documented in the Dictionary: Note that [they] can have alternative forms to take account of the subject's gender as well as the present & past tense forms.
These are specified by adding the suffix _M, _F or _P to the phrase name. _ToBe_Past_M below is an example.
Is this not suitable for your requirement? Let me know the problems then I can work on the solution.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 2 days ago @ 1:39:10 AM
GenoPro Version: 2.0.1.4
Posts: 552,
Visits: 7,227
|
|
| I will. As I wrote before, when I will have a problem, I'll let you know. As for the names translations, is it an automatic procedure in the report generator, or should I add somthing for "sending" the ReportGenerator to translate the name?
I looked in the help files and didn't found anything. In previous versions I wrote my own code for translating the names.
|
|
|
|
|
Grand Master
Group: Customers
Last Login: Today @ 4:04:45 AM
GenoPro Version: 2.0.1.5
Posts: 1,029,
Visits: 4,708
|
|
| Yes, the translation of names is 'automatic' in that no script changes are required. The names and their translation need to be added into a NameDictionary.xml file and then it is necessary to set two Configuration Parameters, LangNames & LangNameDictionary. These can be set via any one of the three methods available, i.e. edit Config.xml in custom skin, create Document Custom Tags with required value or change via the 'Generate Report' dialog window. Each part of Individuals names will be translated from the language code in the LangNames parameter to the language code specified in the Language attribute of the the Skin element in the Config.xml file. PLace names and Occupation titles can also be translated by setting the LangPlace & LangOccupation parameters and adding the required elements & attributes to the NameDictionary.xml (see notes in sample NameDictionary.xml provided with the Narrative skin) ALternatively it is also possible to add a translated name in brackets following the original name in the Report. In this case set Config Parameter TagNameAlternative to the tag to be translated (e.g. Name to translate full name) and set LangAlternative to the code of the language it is to be translated to. e.g. set to HE to add Hebrew translation (where they exist in NameDictionary.xml) following the original names. I have only done limited testing on these features.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 2 days ago @ 1:39:10 AM
GenoPro Version: 2.0.1.4
Posts: 552,
Visits: 7,227
|
|
Ron (7/20/2007)
Yes, the translation of names is 'automatic' in that no script changes are required. The names and their translation need to be added into a NameDictionary.xml file and then it is necessary to set two Configuration Parameters, LangNames & LangNameDictionary. These can be set via any one of the three methods available, i.e. edit Config.xml in custom skin, create Document Custom Tags with required value or change via the 'Generate Report' dialog window.Well, this is the option I chose. I set the LangNames parameter to "Y" and the LangNameDictionary to "NameDictionary.xml" but the names are still in English and are not translated to the Hebrew name which is in the NameDictionary.xml. What am I doing wrong?
|
|
|
|
|
Grand Master
Group: Customers
Last Login: Today @ 4:04:45 AM
GenoPro Version: 2.0.1.5
Posts: 1,029,
Visits: 4,708
|
|
I am not sure of the default path for the NameDictionary.xml. I have always used a full path. Also LangNames must be set to a language code, matching that in NameDictionary e.g. EN if you are translating names from English in your .gno file to your skin language of HE (Hebrew). Each part of Individuals names will be translated from the language code in the LangNames parameter to the language code specified in the Language attribute of the the Skin element in the Config.xml file.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 2 days ago @ 1:39:10 AM
GenoPro Version: 2.0.1.4
Posts: 552,
Visits: 7,227
|
|
Ron (7/20/2007)
I am not sure of the default path for the NameDictionary.xml. I have always used a full path. Also LangNames must be set to a language code, matching that in NameDictionary e.g. EN if you are translating names from English in your .gno file to your skin language of HE (Hebrew). Each part of Individuals names will be translated from the language code in the LangNames parameter to the language code specified in the Language attribute of the the Skin element in the Config.xml file. The NameDictionary elements can have many different language attributes for each name, hence the need to tell the script which one to use. Now its working!!!
|
|
|
| | |