The Ind tags/fields "Title" and "Suffix" cannot be translated
GenoPro Home  |  Get Started With My Genealogy Tree  |  Buy  |  Login  |  Privacy  |  Search  |  Site Map
 
GenoPro Support Forum
Home        Members    Who's On
Welcome Guest ( Login | Register )
        



The Ind tags/fields "Title" and "Suffix" cannot be translated Expand / Collapse
Author
Message
Post #22163 Posted 7/19/2008 5:24:07 AM


Famous Writer

Famous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous Writer This user is a contributor to FamilyTrees.GenoPro.com This user is an important contributor to the translation of GenoPro This user is an important contributor to the GenoPro community 

Group: Customers
Last Login: Yesterday @ 3:31:49 PM
GenoPro Version: 2.0.1.6
Posts: 434, Visits: 1,152
This posting is, I suppose, valid for all languages:

1) Both Enums do not exist within Genopro Language Localization Enum list.
2) Dictionary.xml doesn't show these Enums either and are therefore not processed during a Report Geneerator.

Looking on the Tag Definitions panel, these 2 fields are also shown as "Text" type but not as "Enum" type.
Is it on purpose?
Thank you,
JC

Post #22165 Posted 7/19/2008 8:13:07 AM


Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master This user is an important contributor to the translation of GenoPro 

Group: Administrators
Last Login: Yesterday @ 9:55:00 PM
GenoPro Version: 2.0.1.6
Posts: 3,424, Visits: 14,202
jcguasp (7/19/2008)
Looking on the Tag Definitions panel, these 2 fields are also shown as "Text" type but not as "Enum" type.
Is it on purpose?

An enumeration is a fixed list of values.  Since the user can type anything for the individual title, the field title is therefore text.  The drop down are suggestions for the individual title, such as "Mr", "Ms", "Dr", "Rev".   Ideally those suggestions should be translated, however the current architecture does not allow this without massive code update.

Post #22166 Posted 7/19/2008 9:15:25 AM


Famous Writer

Famous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous Writer This user is a contributor to FamilyTrees.GenoPro.com This user is an important contributor to the translation of GenoPro This user is an important contributor to the GenoPro community 

Group: Customers
Last Login: Yesterday @ 3:31:49 PM
GenoPro Version: 2.0.1.6
Posts: 434, Visits: 1,152
Ok Dan. I forgot we can input data into these fields.

Having said that, I now turn to Ron:
Shouldn't these 2 fields then be Multi-Languistic compatible?
For info, the spaces allowed in the panel are quite restrictive but can be prepared outside the fields and then pasted in!

JC

Post #22171 Posted 7/19/2008 12:58:01 PM


Grand Master

Grand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand Master This user is a contributor to FamilyTrees.GenoPro.com This user is an important contributor to the GenoPro community 

Group: Customers
Last Login: Yesterday @ 5:37:53 PM
GenoPro Version: 2.0.1.5
Posts: 1,077, Visits: 4,922
The Narrative Report does not access the Title & Suffix fields directly, instead it translates (e.g. via NameDictionary) the Name property that GenoPro creates using the Name.Format property, that may or may not include the title and suffix fields.

Therefore perhaps a solution would be to put translations into the NameDictionary e.g. FR="Mme" EN="Mrs".

The script cannot use the Name.Format to derive the components of Name since Name can also be free text.


'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
Post #22173 Posted 7/19/2008 2:32:20 PM


Famous Writer

Famous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous Writer This user is a contributor to FamilyTrees.GenoPro.com This user is an important contributor to the translation of GenoPro This user is an important contributor to the GenoPro community 

Group: Customers
Last Login: Yesterday @ 3:31:49 PM
GenoPro Version: 2.0.1.6
Posts: 434, Visits: 1,152
Thank you Ron.

1)The translation works OK via NameDic. That is for the main Rep Gene.

My associated entries in NameDic:

2) For the Descendants Rep, as shown on the following screenshot, my Places are being translated OK but not these 'Title' and 'Suffix' fields.

3) Additional question: For any other Rep including the Ancestors one, once NameDic has been copied into the skin Rep Dir, is it possible to access NameDic from the script? and how?

JC

Post #22177 Posted 7/19/2008 7:22:12 PM


Grand Master

Grand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand Master This user is a contributor to FamilyTrees.GenoPro.com This user is an important contributor to the GenoPro community 

Group: Customers
Last Login: Yesterday @ 5:37:53 PM
GenoPro Version: 2.0.1.5
Posts: 1,077, Visits: 4,922
Whoops, another bug in Descendants Report. As you have discovered, JC, the partial name translation does not work. The attached utils.js that you can replace in a custom skin fixes it.

The NameDictionary.xml file is accessed via the Report Generator Util.NewNameDictionary method and the NameDictionary Class

Look for BuildLookupTable in the Narrative Report Init.htm file and the Descendants Report Code\GenoProParser.js file for ideas on building the tables used. The VBScript functions StrNameTranslate & StrPlaceTranslate in Code\Lang.vbs and the JScript String object prototype methods translate, translateName, translatePlace in Code\utils.js show how I have implemented translation.


'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"


  Post Attachments 
Utils.js (2 views, 7.50 KB)
Post #22179 Posted 7/20/2008 6:47:42 AM


Famous Writer

Famous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous WriterFamous Writer This user is a contributor to FamilyTrees.GenoPro.com This user is an important contributor to the translation of GenoPro This user is an important contributor to the GenoPro community 

Group: Customers
Last Login: Yesterday @ 3:31:49 PM
GenoPro Version: 2.0.1.6
Posts: 434, Visits: 1,152
Sorry Ron. Still doesn't translate.

Update:
1) In your new Utils.js, I added a debug LogWarning ligne, to monitor sPart & sTrans variables, immediately after your ligne 71 -> sTrans = oNameDic(sPart);
and got this:

There's many warnings but all identical!
For the Rep , I selected a single Ind (without Descendants) but with a Name Title and Suffix.

2) I noticed something else: my place United Kingdom -> Royaume-Uni has been translated OK but not the preposition:

here is my NameDic entries:

3) For info, the main Rep is OK.

JC

Post #22182 Posted 7/20/2008 9:49:50 AM


Grand Master

Grand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand MasterGrand Master This user is a contributor to FamilyTrees.GenoPro.com This user is an important contributor to the GenoPro community 

Group: Customers
Last Login: Yesterday @ 5:37:53 PM
GenoPro Version: 2.0.1.5
Posts: 1,077, Visits: 4,922
jcguasp (7/20/2008)
Sorry Ron. Still doesn't translate.

I'm the one who should say sorry. I tested the Title translate fix elsewhere, and then merged the changes in my update folder but did not retest. Of course I missed one of the changes. So attached is a tested file. I'll look into the preposition translation issue later.



'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"


  Post Attachments 
Utils.js (2 views, 7.50 KB)
« Prev Topic | Next Topic »


Reading This Topic Expand / Collapse
Active Users: 0 (0 guests, 0