|
|
|
Forum Master
 
 
Group: Customers
Last Login: 2 days ago @ 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
I am not sure what you mean. Do you mean that GenoPro will translate the names automatically without any need for the user to write code? Yes. For instance, the Config.xml could have a tag: This way, GenoPro would automatically load the NameDictionary.xml and perform a name lookup (translation) for every individual and place within the genealogy tree before starting generating the report. In other words, this name translation would be transparent to the report templates.
It sounds like a great idea. If GenoPro can do it automatically it would be great. The user wont need to go over the code and add the code for the translation.
As for the Beta 13j I will try to generate the report with it.
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 2 days ago @ 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
OK.
I tried it and it worked just fine for me. The names I entered to the NameDictionary.xml were translated and the rest remained the same.
Will the names and surnames will be at the same table and xml file?
Should I work with the NameDictionary.xml now or wait for the built-in tool?
I do see trouble with the skins. In each Beta version there can be some modifications to the /English skin. Some of them are crucial, because we are talking about Methods changed.
The problem is that that I have to check where all the changes are and modify all my skins with the changes. Otherwise they wont work...
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Yesterday @ 11:13:07 PM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,173
|
|
The names I entered to the NameDictionary.xml were translated and the rest remained the same. My question is the following: Is the use of NameDictionary.xml a solution for translating names? Is there anything missing in this solution? Would it be better to have another dialog named "General HE" for entering the names in Hebrew within GenoPro?
Will the names and surnames will be at the same table and xml file?
Should I work with the NameDictionary.xml now or wait for the built-in tool? If the NameDictionary.xml solution works for translating names, I will write some code within GenoPro to edit the file NameDictionary.xml. GenoPro can build a list of all unique names, so you only have to type the translated name.
I do see trouble with the skins. In each Beta version there can be some modifications to the /English skin. Some of them are crucial, because we are talking about Methods changed. The problem is that that I have to check where all the changes are and modify all my skins with the changes. Otherwise they wont work...
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 2 days ago @ 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
My question is the following: Is the use of NameDictionary.xml a solution for translating names? Is there anything missing in this solution? Would it be better to have another dialog named "General HE" for entering the names in Hebrew within GenoPro? When I first thought about the name translation I thought of a simple xml file to read from and write to. What I asked for was only a method or two within the report generator to read from the file.
I think that what we came up with is a better solution, especially for those who don't know anything about programming and they stil want to use the report generator. Therefore any build-in solution that enables the simple user to maintain the name translation easily is better.
Would you prefer to have XML sectionss for given names, surnames, and perhaps places? GenoPro can build the lookup table by merging all of them if necessary. Having sections may offer benefits in the future to classify information, and tweak/customize the translation. At first, I wanted the NameDictionary.xml to be simple, but adding sections is not difficult at all. I think that different sections are better because it will be easier to maintain the xml file. If you will add the build-in translation tool it will help to distinguish between the different lists, so the user will know weather he updates the surnames list or the given names list. You will be able to add other tables in the future like the places, occupation, education etc.
If the NameDictionary.xml solution works for translating names, I will write some code within GenoPro to edit the file NameDictionary.xml. GenoPro can build a list of all unique names, so you only have to type the translated name. I think this is what we talked about. A list of unique names and the ability to translate them to any other language that the user wants.
This is a problem everywhere. I use Windiff to compare modifications between files and perform the merging if necessary. The trick is to keep a backup of your work before upgrading, so you can compare what has been upgraded. Windiff is a free tool you can download almost everywhere ( http://www.grigsoft.com/download-windiff.htm - 75 Kb) |
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Yesterday @ 11:13:07 PM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,173
|
|
Great, this is what I wanted to read. I am currently working on a Privacy Filter to hide some information while generating a report. For instance, the privacy filter allows to hide contact information on a report.
I will work on this name translation next, because I consider it part of the report generator. As for deleted methods, there are only two at the moment: LanguageDictionary.Individuals() and LanguageDictionary.Families(). I forgot to remove them when I released the betas. In the future, I will have a page about new methods and deleted methods. In the meantime, if you see an error or have a question, post a message and I will help you.
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 2 days ago @ 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
Thanks.
I did found those methods and removed them with the new ones.
I do think that you are doing a great job in making GenoPro a multi-lingual software.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Yesterday @ 11:13:07 PM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,173
|
|
I do think that you are doing a great job in making GenoPro a multi-lingual software. It is all of the feedback I am getting from users like you. I have plans to improve the multi-lingual reports. For instance, a single report skin will be capable to support multiple language dictionaries, say LanguageDictionary.xml, LanguageDictionaryHE.xml, LanguageDictionaryFR.xml, and so on. GenoPro will load the proper language dictionary before generating the report. A new method named ReportGenerator.SkinLanguage will return the language code such as "EN","HE", "FR" so the developer can write VBScript/JavaScript code for a specific language if necessary. This way, the same skin template can be re-used for multiple languages.
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 2 days ago @ 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
What I think will be great is for the report generator to be able to create all kinds of reports not just HTML but word documents (doc and rtf), pdf files and so on.
Users can then use it to create their own books and reports.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Yesterday @ 11:13:07 PM
GenoPro Version: 2.5.0.2
Posts: 3,638,
Visits: 15,173
|
|
I agree. I think supporting VBScript and JavaScript is a step in the right direction. With time, new features will be added. I truly believe the report generator is stake of GenoPro's future.
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 2 days ago @ 4:44:18 PM
GenoPro Version: 2.0.1.6
Posts: 552,
Visits: 7,390
|
|
| So this is the plan for GenoPro v. 3? :D
|
|
|
|