GenoPro Support Forum

update: lang.vbs not needed anymore

dictionary_ja.zip (17 views, 29.56 KB)

Edited: Saturday, June 30, 2007 by maru-san

I will get back with the report generator to improve it after version 2.0.  I understand the report generator is not finished yet, however it is usable.  I am happy the report generator is working at all, because this was brand new technology to me.  I have many ideas to make the report generator more powerful and than it is now. 

I am thinking of adding the attribute Language to each elemen in Config.xml, so the report generator can pick the file "homeJA.htm" or "homeHE.htm" when generating the report.  If there is more HTML code, it will be easier to have a different HTML file for each language, than moving everything in the dictionary file.

At the moment, I am working on Bet15 for the social entities.  I use the name "Social Entity" to describe a school, church, club, committee, council, advisory group, organization, partnership, business or corporation.  Then, there are "Social Activities" and "Social Relationships" such as managing, funding, investing, coaching, customer of, associate, partnership, and more.

Lets finish ver 2 first

This solution could would work for any text field.  I have to figure out a good user-interface for a single-line field but it can be done.  By the way, this feature will be for version 3.0.

That sounds like a grea idea. Can't this be the solution for all the fields? Can't GenoPro work in the same way in all the other fields in the gno file?

That is the goal, except the solution I am thinking allows multiple languages instead of 2.  GenoPro will not attempt to translate comments (because it is nearly impossible to do so), but will allow the same comment to be written into multiple languages.

Since translation of comments is a big problem, why not making it possible to write comments on genopro in 2 languages manually, and the report generator will use the relevant comment depending the language that the user choose to create a report

Edited: Friday, September 9, 2005 by GenoProSupport

I have been thinking of a solution for supporting multiple languages per comment.  GenoPro can recognize a the language code (EN, FR, JA, HE) at the end of each field such as i.birth.comment.EN, i.birth.comment.FR, i.birth.comment.JA, i.birth.comment.HE.  When generating the report, GenoPro can select the proper language code.  If no text is found under the given language code, GenoPro could optionally select the neutral language if any (eg: i.birth.comment).

On the graphical interface, a drop-down list would be available to the user to add a new comment in a new language.  Internally, GenoPro would use a clever mechanism to store and classify text for each language.

This way, there would be no need to have two trees. A single .gno file could store as many languages as necessary.  The Table Layout would have problems to display the same comment in multiple languages, so I am thinking the Table Layout should display one language (the language selected by the user).

There is also a discussion for descriptions in multiple languages.

To the line: