|
|
|
|
Customers
Important Contributors
Translator
GenoPro version: 3.1.0.1
Last Login: Friday, November 25, 2022
Posts: 334,
Visits: 7,574
|
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.
|
|
|
|
|
Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: 1 hour ago
Posts: 4,886,
Visits: 22,776
|
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.
|
|
|
|
|
Gamma
Customers
Important Contributors
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: Monday, March 24, 2025
Posts: 257,
Visits: 2,860
|
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)
|
|
|
|
|
Customers
Important Contributors
Translator
GenoPro version: 3.1.0.1
Last Login: Friday, November 25, 2022
Posts: 334,
Visits: 7,574
|
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?
|
|
|
|
|
Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: 1 hour ago
Posts: 4,886,
Visits: 22,776
|
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.
|
|
|
|
|
Gamma
Customers
Important Contributors
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: Monday, March 24, 2025
Posts: 257,
Visits: 2,860
|
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)
|
|
|
|
|
Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: 1 hour ago
Posts: 4,886,
Visits: 22,776
|
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"?
|
|
|
|
|
Customers
GenoPro version: 2.5.4.1
Last Login: Friday, October 18, 2013
Posts: 142,
Visits: 3,822
|
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
|
|
|
|
|
Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: 1 hour ago
Posts: 4,886,
Visits: 22,776
|
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?
|
|
|
|
|
Customers
GenoPro version: 2.5.4.1
Last Login: Friday, October 18, 2013
Posts: 142,
Visits: 3,822
|
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
|