|
|
|
Forum Master
 
 
Group: Customers
Last Login: 11/19/2009 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
I'm using English as my family tree language because I have relatives all over the world. My language is Hebrew.
I dont want to have two family trees to maintain (English + Hebrew).
So
I thought of an idea.
The dictionary.xml file lets me generate a report in Hebrew for my tree. The problem is that the name (first + last) will be in English.
I thought of using the dictionary.xml to translate names from English to Hebrew. I tried it and it worked.
However - the list of names and surnamesis very long.
my question:
I want to create a new xml file that will hold all the names and surnames I want.
Is there any methods within the Report generator that I can use to retrieve information from the xml file (like the LanguageDictionary method)?
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 1:16:25 AM
GenoPro Version: 2.5.0.2
Posts: 3,639,
Visits: 15,178
|
|
At the moment, the LanguageDictionary object has only two methods: Lookup and Peek. Both method return the translated text, however Peek does not display any error if the string identifier is not there.
The LanguageDictionary was designed to be very performant, so it uses a hybrid data structure, and this is the reason why there are no other built-in methods to iterate. Of course, I can add new methods. Would it be better to have a separate XML file for this purpose?
What about modifying GenoPro to have fields regarding translation, similar to DoroTree?
|
|
|
|
|
Forum Master
Group: Customers
Last Login: Today @ 3:49:44 AM
GenoPro Version: 2.0.1.6
Posts: 758,
Visits: 6,292
|
|
I started all my trees in english, but then I thought about all my german and japanese relatives.
So for me it's like keeping one english xml for all and one xml especially for japanese. As far as reports are going I have to make three dictionaries for three kind of reports such as english with First and Last Names and all education, occupation and comments, no translation necessary.
Then one dictionary for german and also modifying the reports, however I would like to skip all comments for educations, occupations and pictures by some kind of selection mode beforehand and then one for japanese using only Alternative Names with the same selection as for german. The reports (html) to be translated correspondingly. A table style layout would be more suitable than a narrative style.
Modified the report of "ron" into german and modified the individual.htm. The first part looks ok now with me, but when it comes to education and occupation and! comments it is just too much to ask for. So it will be a stripped down report to basic information.
So the request goes for a very straight forward reporting style with the possibility for selections (included in report yes/no), This will make the translation a lot easyer.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 1:16:25 AM
GenoPro Version: 2.5.0.2
Posts: 3,639,
Visits: 15,178
|
|
maru-san (8/18/2005)
So the request goes for a very straight forward reporting style with the possibility for selections (included in report yes/no), This will make the translation a lot easyer.
Can you elaborate a bit more on this? I don't understand. By the way, I am adding new methods to better take advantage of the language dictionary. My goal is to have GenoPro capable to use a true universal HTML template, where all the language-dependent text is stored in the language dictionary.
|
|
|
|
|
Forum Master
Group: Customers
Last Login: Today @ 3:49:44 AM
GenoPro Version: 2.0.1.6
Posts: 758,
Visits: 6,292
|
|
| My suggestion is when you open the dialog box for making your report, you will have under option not only the path of pictures but actually the choice what you want to have included in the report (which name, education yes/no, occupation yes/no, comments yes/no, etc.). Whether this can be done is another question.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 1:16:25 AM
GenoPro Version: 2.5.0.2
Posts: 3,639,
Visits: 15,178
|
|
What you requested is not a problem at all. In fact, all the tags in the <Parameters> in Config.xml will be accessible from the report dialog. In the configuration file, you will be able to define whatever the parameter is plain text or a list of options.
In the meantime, you have to manually edit Config.xml using Nodepad.
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 11/19/2009 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
The LanguageDictionary was designed to be very performant, so it uses a hybrid data structure, and this is the reason why there are no other built-in methods to iterate. Of course, I can add new methods. Would it be better to have a separate XML file for this purpose? What about modifying GenoPro to have fields regarding translation, similar to DoroTree?
First - as I understand it the LanguageDictionary is looking only in the <ReportGenerator>
section of the dictionary. If I put my translated names there I can do what I want but the list is going to be a very long one, so I thought that it is better to put them in their own file. It will be also easier to maintain the list there.
As to modify GenoPro to have fields regarding translation similar to DoroTree, of course it is the better solution.
In my method, however:
1. There is no need for such fields.
2. I don't have to translate first and last names for every individuals in my tree, I only have to do it once in the Names.xml file.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 1:16:25 AM
GenoPro Version: 2.5.0.2
Posts: 3,639,
Visits: 15,178
|
|
Should GenoPro store those translated names in the .gno or .xml file? GenoPro could have a list of translated names, and the report generator having a method such as Util.GetTranslatedName("morin") returning the translated name.
Of course, a an external file names.xml could also be used, as a "default" lookup if there is no names found in the .gno file.
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 11/19/2009 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
Should GenoPro store those translated names in the .gno or .xml file? GenoPro could have a list of translated names, and the report generator having a method such as Util.GetTranslatedName("morin") returning the translated name.
If you are talking about my suggestion (no special fields in GenoPro) - GenoPro needs only to add a method of retrieving information from an xml file. The maintance of this file is on the user, not GenoPro. The method should be somthing like: Util.GetXMLValue (xmlFile, LookUpVal) or Util.GetXmlValue (xmlFile, xmlSection, LookUpVal).
On the other hand if you are talking about additional fields then GenoPro can store it on the .gno file since it can be retrieved as any other field.
|
|
|
|
|
Famous Writer
Group: Customers
Last Login: 10/31/2009 1:39:55 PM
GenoPro Version: 2.0.1.6
Posts: 438,
Visits: 2,595
|
|
Wouldn't it be complicated for user to have data stored in two different files!
Shouldn't single source for data be *xml OR *gno file... the other one just might exist as a backup?!
- "εν οιδα οτι ουδεν οιδα" (Σωκρατησ) - "The only thing that I know is that I don't know anything" (Socrates)
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 11/19/2009 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
V.L.o (8/18/2005)
Wouldn't it be complicated for user to have data stored in two different files!
Shouldn't single source for data be *xml OR *gno file... the other one just might exist as a backup?!
It is not data in different files!!
You can call it a names dictionary.
If you want to translate your reports to other language you are modifying dictionary.xml to your language. You are only translating not keeping duplicate data. It is the same in the names.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 1:16:25 AM
GenoPro Version: 2.5.0.2
Posts: 3,639,
Visits: 15,178
|
|
GenoPro could have a small table in the "Tools" menu for name translation. One column could be English and the other column could be some other language such as Hebrew. You would then enter all the names you want to be translated without having to know any XML. This table would be automatically be stored in the .gno file, and could be exported to an external XML file, so it can be re-used in another .gno document. GenoPro would then provide a built-in mechanism to perform name translation while generating reports.
The LanguageDictionary is already an object on its own. I could have a method named Util.NewLanguageDictionary(strFileXML, strSectionXML) to create a new language dictionary from a section within an XML file. This way, all the methods of the LanguageDictionary object such as Lookup and Peek would be available to the user. I plan to add several methods to the LanguageDictionary object.
Ideallly, the method Util.NewLanguageDictionary would be called at the begining of the report, and the returned language dictionary object would be stored in the Session object.
|
|
|
|
|
Famous Writer
Group: Customers
Last Login: 10/31/2009 1:39:55 PM
GenoPro Version: 2.0.1.6
Posts: 438,
Visits: 2,595
|
|
It seams as a much better idea!
As it happens, most computer users are more or less computer illiterate persons... They just want to have something that works it's job (with as less tuning as possible) and don't want to know how it works...
- "εν οιδα οτι ουδεν οιδα" (Σωκρατησ) - "The only thing that I know is that I don't know anything" (Socrates)
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 11/19/2009 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
GenoPro could have a small table in the "Tools" menu for name translation. One column could be English and the other column could be some other language such as Hebrew. You would then enter all the names you want to be translated without having to know any XML. This table would be automatically be stored in the .gno file, and could be exported to an external XML file, so it can be re-used in another .gno document. GenoPro would then provide a built-in mechanism to perform name translation while generating reports.
This sounds like a very good idea. Can GenoPro automatcally take all the names / surnames in the tree and put them in this table, or the user will enter the names and translations?
will the names and surname be in the same table or they will be separated?
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 1:16:25 AM
GenoPro Version: 2.5.0.2
Posts: 3,639,
Visits: 15,178
|
|
GenoPro can populate the table with all unique names (first name, middle, last, second last, alternative). This mechanism could be extended for places (cities, provinces/states).
All you would have to do is to enter the equivalent translated name in the next column. GenoPro could easily offer multiple columns for different languages such as "EN" (English), "HE" (Hebrew), and say "JA" (Japanese). During the initialization of the language dictionary, you could specify which translation you want. If none is specified, GenoPro would default to the second column.
My question is: Would that solution work for you? It is almost too good (easy) to be true.
|
|
|
|
|
Famous Writer
Group: Customers
Last Login: 10/31/2009 1:39:55 PM
GenoPro Version: 2.0.1.6
Posts: 438,
Visits: 2,595
|
|
Would it be pushing if the default 2nd language name would be some original form of Name (I sometimes placed such data under Nickname)?
It could work, at least for me!
- "εν οιδα οτι ουδεν οιδα" (Σωκρατησ) - "The only thing that I know is that I don't know anything" (Socrates)
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 1:16:25 AM
GenoPro Version: 2.5.0.2
Posts: 3,639,
Visits: 15,178
|
|
Pushing is good. GenoPro is about pushing the limits of genealogy software to reach new levels of genealogy computing.
V.L.o (8/18/2005)
Would it be pushing if the default 2nd language name would be some original form of Name (I sometimes placed such data under Nickname)?
What do you mean by "original form of Name"?
|
|
|
|
|
Forum Guru
Group: Customers
Last Login: Yesterday @ 11:04:20 AM
GenoPro Version: 2.0.1.6
Posts: 140,
Visits: 2,224
|
|
My question is: Would that solution work for you? It is almost too good (easy) to be true.
I'm all for it. It sounds like a good idea. We should note that the translation is not always exactly the same each time. There should be a way to override for a specific individual.
I will give an example: The name Chaim in Hebrew can be translated to Haim, Chaim or Howie in English. The reverse translations are not always 1:1 either.
Danny
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 1:16:25 AM
GenoPro Version: 2.5.0.2
Posts: 3,639,
Visits: 15,178
|
|
Well I am glad this solution would work for you. The more "votes" I get, the more confident I am with this solution. You have to understand, I only know French and English, and therefore it is difficult for me to truly grasp the challenges you are facing.
Would you like the translation only in the report, or also in the GenoPro application?
I will give an example: The name Chaim in Hebrew can be translated to Haim, Chaim or Howie in English. The reverse translations are not always 1:1 either.
What can be done in this case. Would specifying the Permanent ID of that individual solve the problem?
|
|
|
|
|
Forum Guru
Group: Customers
Last Login: Yesterday @ 11:04:20 AM
GenoPro Version: 2.0.1.6
Posts: 140,
Visits: 2,224
|
|
Would you like the translation only in the report, or also in the GenoPro application?
Both, I think. With an ability to override, by using specific fields. In this manner, we can have the best of both worlds.
Here is what I envision:
Having a standard set of translations of names, so that when entered in the Name field, the translation would appear automatically in the Foriegn Name field. Then we can override this name by specifying a new one in that same Foriegn Name field.
Optimally, perhaps we can have multiple translations, and one would have to be chosen from a list in the Foriegn Name field. This would work by defining a name to translate, with multiple choices, e.g.:
Chaim -> Haim / Chaim / Howie
One of these would be selected upon insertion of a new name, or an update of an existing name, based upon the drop-down list created automatically.
A translated name can be fed back into the dictionary table, thus removing the need for non-techies to update manually. In addition, a table created expressly for this purpose can be brought up, just as a table of individuals or pictures (under View - table layout...), where insertions / deletions / updates can be made by the non-techie.
Reports would automatically look at the translation table, unless something already appears in the Foriegn Name field. This can be a setting of the report, i.e.: Auto-translate names?
Bottom line: the translation has to be specific to individuals.
I hope the description does not cause you to go into a programming warp of great deal of time. On the other hand, I think it would only enhance the program.
Danny
|
|