By genome - Friday, May 25, 2007
|
I have attached a revised English Narrative Report skin. This covers some of the later issues in topic http://support.genopro.com/Topic17661-60-1.aspx. The main changes are a few more translation aids that were not ready in time for 2.0.0.5. The skin contains a ChangeLog.txt file outlining the changes to Dictionary.xml for those of you who have translated it to other languages. The main change is in place prefixes, prepositions or 'locative' cases. If you add two Custom Tags to the Place object, namely Name.Gender & Name.Plural, then the Dictionary entries can take account of the gender of a Place name and its plurality. So we can have a place 'Pays-Bas' with an automatic prefix and set its Name.Plural Custom Tag to 'Y' and a Place France with Name.Gender set to 'F' to use the Dictionary entries <PlacePrefix_Country T="au" P="aux" /> to arrive at aux Pays-Bas and <PlacePrefix_Country_F T="en" /> to get en France
(hopefully next week I'll include name translation to translate 'Holland' to 'Pays-Bas' via the NameDictionary) similarly in German we can have <PlacePrefix_AtThe T="in dem" /> <PlacePrefix_AtThe_F T="in der" /> |
The other major change is expanded forms of the date span phrases. Note that I have removed the leading space from these phrases and so Dictionary phrases that use them have also been changed. Minor changes are a facility for gender-specific terms for twins and possessive forms the the 'spouse/mate' alternatives. Also a little tweak to Timelines to have a minimum gap of 30 pixels for events sharing the same timeline 'track' as I found it looked odd when two events occurred 'back-to-back'. Update: 4 Jun 2007 - 2.0.0.6RC2 posted Update: 7 Jun 2007 - 2.0.0.6RC3 posted Update: 18 Jun 2007 - 2.0.0.6RC4 posted Update: 23 Jun 2007 - 2.0.0.6RC5 posted Update: 26 Jun 2007 - 2.0.0.6RC6 posted
|
By jcguasp - Sunday, May 27, 2007
|
I modified my FR skin, adding all the changes appearing in Ron's latest skin R006rc1 and got this error when generating an FR report: The so-called invalid char are actually "é". Possibly a unicode problem. Thank you.
|
By genome - Sunday, May 27, 2007
|
That is strange. I changed line 41 in my Dictionary to <cremation T="son corps a été incinéré"/>
| and the report generated without any errors or warnings.
|
By maru-san - Sunday, May 27, 2007
|
Had the same problem with my dictionary file. So instead of modifying my file, I modified Ron`s dictionary file and moved my translation to that file(troublesome). This was faster then trying to find the culprit, which caused this.
|
By jcmorin - Monday, May 28, 2007
|
When saving your file containing accent or non ASCII characters make sure your file is saved in Unicode UTF-8 and not the local codepage of your system. Even notepad have this option in the save as dialog.
|
By jcguasp - Tuesday, May 29, 2007
|
Thanks, JC, for the "UTF-8 save as" tip. It's OK now. Some more small requests for FR (and probably for other Lang) translations. Also a few noticed bugs. A - Translation matters 1) <Unknown> There is a need for a Fem trans of this sub-title (Inconnu -> Inconnue) based on the Ind Gender.2) Adoptif fils (adopted son): The FR word order should be "Fils adoptif". To achieve this at the moment, the instruction "WriteIndividualEvents ..." needs to be changed within "Util.vbs", if not mistaken. This should be accessible from the Dic. Also the adjective "Adoptive" should also be provided for a Fem Ind, i.e. <TimelineAdopted_F>. Also, perhaps for other languages, a <TimelineFoster_F>. 3) Connu (known) There is a need for the plurial of the adjective "Connu", i.e. in the <PhChildRank> template. I'm no French teacher but, as the word "enfant" could, in fact, be Masc (un enfant) or Fem (une enfant), I wonder if a Fem Plurial (connues) should also be provided (when all chidren are Fem)? Up to Genopro to check this point. B - Bugs 1) Half-sisters phrase not complete. It should say "... et <inconnue>" (unknown Fem). 2) Space before a year This only happens in a Pedigree Chart: 3) Missing "d" in Date "de" The bug, apparently, may not be fully fixed yet! I think it's only when a month is present. For info, here are the associated Ph templates: <FmtSinceYM>[à partir de|aux environs de|avant|après] MMM yyyy</FmtSinceYM> and <FmtFromYM>[de|aux environs de|d'avant|d'après] MMM yyyy</FmtFromYM> Note: The <ConvertDateSpan> substitution template doesn't seem to be implemented, i.e. de -> d' in front of avril, août and octobre. Same remark for the <LocativeProperNoun> subst templ: Doesn't seem to work. I'll test a bit more if I've got time, including the Places Prefix as explained in the 1st post of this topic. There's so many possible scenarios all over the place!! I am also looking forward on the implementation of the new "NameDictionary.xml". Looks interesting. Good work. JC
|
By genome - Friday, June 1, 2007
|
Some more valid points Jean-Claude that in the main appear quite straightforward to address. Some I have already coded solutions. I'll need to do some more checks on the substitution problems you have found as I thought they we working. I want to include a new 'Report Parameters' dialogue that I am currently working on in the next release and I also need to do some further work for name translation so it will be a few days before I have the next release candidate ready.
|
By jcguasp - Saturday, June 2, 2007
|
Thanks Ron. Here are a few more translation requests: 1) Contact entries Subsequent to clicking an entry in the Contact Toc, I noticed some Ph not fully translated: I then changed, in Contacts.htm, the line: Report.WritePhraseDic "PhOccupancy", c.type, StrHtmlHyperlinkPlace(c.Place), c.Duration, c.DateStart.FormatDateSpan(c.DateEnd) to (copied from the Sub WriteHtmlOccupancies(i) in Ind.htm): Report.WritePhraseDic "PhOccupancy", c.type, StrHtmlHyperlinkPlace(c.Place), c.Duration, StrDateSpan(c.DateStart, c.DateEnd) and it seems OK (except a disappearing "d" already mentioned somewhere else). Of course, Ron to check. Note on *: We can see the presence of "0 mois" (0 months). I also noticed the same in View Table Layout: I suggest Genopro to review the calc routine and to remove from field any zero Y, M or D. 2) Godparent Social Relation In FR, There's no translation for "Godparent". Only "parrain" and "marraine" for "godfather" and "godmother" respectively. So Genopro to decide what to do? Perhaps to provide a <PhSR_Godparent> _M & _F? 3) Sources a- The Confidence level field is not narrated. Is it on purpose? b- The narrative doesn't show a PlacePrefix for the Repository field That's it. Now waiting for your next release. JC
|
By GenoProSupport - Sunday, June 3, 2007
|
I will take a look at those issues.
|
By genome - Monday, June 4, 2007
|
Hopefully all of Jean-Claude's points, other than the GenoPro '0 mois' or '0m' issue have been resolved in 2.0.0.6RC2 which is now available see the 1st post of this thread. I cannot reproduce the missing 'd' (i.e. de becomes e) problem. Could you confirm, Jean-Claude, that you are using the 'DateFix' version of 2.0.0.5? http://support.genopro.com/FindPost17847.aspx Regarding the 'godparent' phrase, The 'PhSR....' phrases did already have parameters for '3 subject female?' and '4 object female?' but I had wrongly annotated these as '3 subject gender' & '4 object gender'. The 'godparent' social relationship now shows godmother or godfather as appropriate. The 'ConvertDateSpan' feature was in fact working but my commented French example had an extraneous apostrophe causing it not to work. Similarly with 'LocativeProperNoun', I forgot the leading space in the commented French example. The Dictionary has now been corrected. This version has an optional dialogue allowing Configuration parameters to be viewed and changed at Report generation time. All text for this dialogue is in the Dictionary and so can be translated. The interface is a little 'clunky' as VBscript in the Report Genenerator has no 'sleep' or 'wait' facility other than that present as part of the 'Popup' prompt method. P.S. just realised I have not updated the 'ChangeLog.txt' for this version. I will correct this tomorrow. Other additions are the facility to translate place names via a NameDictionary and also to add an 'alternative name' to individuals, either via a name Tag such as Name.Alternative or by translation of another name Tag using the NameDictionary. I still intend to provide full name translation via the NameDictionary and also indexing via the 'base' or 'root' version of a last name.
|
By jcguasp - Wednesday, June 6, 2007
|
To Ron: I re-loaded your 2.0.0.5 DateFix file and it's OK. No more disappearing "d". However, I found something new: The underlined red months are shown as numeric. This only happen when a day is present. When I remove the days (3 & 18), the months are back in letters. Strange. JC
|
By genome - Wednesday, June 6, 2007
|
Thanks JC, you help and rigorous testing is much appreciated. It looks like the 'gremlins' have been at work again. The commented French example in Dictionary.xml contains <FmtToMD>[au |environ au |à l'avant le |à l'après le ]dMM yyyy</FmtToMD> I think this should be
<FmtToYMD>[au |environ au |à l'avant le |à l'après le ]d MMM yyyy</FmtToMD>
|
By maru-san - Wednesday, June 6, 2007
|
Ron, I am receiving following error message
Error at line 1118 (Code/Util.vbs) generating 'Watanabe-Michiko-michikode.htm': 型が一致しません。: 'GetParameter' Microsoft VBScript runtime errorー 800A000D when using your latest skin template. Had made a small test file with 3 individuals, all of them with movie clips.
|
By jcguasp - Wednesday, June 6, 2007
|
Thanks Ron, I already noticed the wrong <Fmt...> in Dic and corrected it (don't forget to also correct the tag closing bit). The problem was I had "MM" (numeric) instead of "MMM" (short 3 letters month). I now even opted for "MMMM" (full letter month). 2 more requests. Both apply to the new Param Config prior to a Rep Gene:1) how can the following 2 buttons be translated: 2) When changing parameter(s) within the table, I noticed the changes are not written back to Config.xml. Can it be done? I didn't notice any major problem with my FR report now. I'll continue testing anyway. Also waiting for the NameDic operability/support. Good work Ron. Thank you. JC
|
By genome - Thursday, June 7, 2007
|
I have now uploaded 2.0.0.6RC3 to the 1st post in this thread. It includes the feature for name translation via a NameDictionary file and also grouping similar last names by a 'root' or 'base' name in the Individual index, the root names are also obtained from the NameDictionary. Many surnames change over time and in some languages the name ending changes with the next generation or the gender of the person. This feature allows all such variations to be listed together. Name translation is also applied to SVG diagrams but may not be suitable in all cases as any bounding box is left unchanged. Comments in the sample NameDictionary.xml file included in the skin give some hints on usage. The Configuration parameter LangNames specified the source language used in the .gno file, whilst the Skin Language determines the target language. All Config params can of course be set as Document Custom Tags or changed when the Report is generated via the Settings dialogue. Place names are translated if LangPlace is set. The ChangeLog.txt file has now been updated with Dictionary.xml changes since 2.0.0.5 I have fixed the issue with GetParameter raised by maru-san. I had moved this function to Init.htm forgetting it was used by the 'Custom Markup' routines to obtain Document Custom tags. I have now changed the CustomTag function to handle these tags. Regarding the two points you raised, Jean-Claude: 1. Language for buttons on VBScript's 'Popup' method. I had expected this to change with the user's locale, as is the case with other Microsoft functions, but this does not appear to be the case. I have tried several variations of Regional Settings in the Control Panel without success. I wonder if Dan has come across a similar issue during conversion of GenoPro to other languages. A possible solution would be for Dan to provide a 'prompt' method as part of the Report Generator that would allow user specification of button text. 2. Saving configuration settings in Config.xml. Whilst it is technically feasible to rewrite the whole of Config.xml file with the new values I am reluctant to do this for two main reasons, i) It would not be possible unless a customized skin was being used, i.e. not 'built-in' to GenoPro. ii) the current Report Generator only provides 'read' functions, with no 'write-back' methods or writeable properties, and so the script would need to replace the entire Config.xml file
Dan has indicated previously that he intended to add a 'parameters' dialogue to GenoPro, but I don't know if or where it is on the roadmap. In the meantime I would recommend setting new values that you want on a more permanent basis using Document Custom Tags in your .gno files.
Thanks for pointing out the closing tag for <FmtToYMD>, i had missed that. I think this version completes the changes I had planned, but if I get time I will look at providing a facility for holding different language versions of comments and other text fields.
|
By maru-san - Thursday, June 7, 2007
|
Ron, found one more issue to be clarified:
`PhPlaceDescription T="The place {!0} ................[ in {7}]............... /` in some instances you do have "in" and in other cases you have "in the", like in: in America, but in the United States of America in South Korea, but in the Republic of ..... or in the Phillipines, there are a few more.
|
By Nand - Thursday, June 7, 2007
|
Ron, in your reply http://support.genopro.com/FindPost18004.aspx I see the following: <FmtToYMD>[au |environ au |à l'avant le |à l'après le ]d MMM yyyy</FmtToMD> I presume that should be: <FmtToYMD>[au |environ au |avant le |après le ]d MMM yyyy</FmtToMD> (dropping the " à l' ")
|
By jcguasp - Thursday, June 7, 2007
|
Hi Nand, Don't ask Ron as he's not a FR specialist. Here's my translation: <FmtDateRange> <FmtSinceYMD>[à partir du|aux environs du|avant le|après le] d MMMM yyyy</FmtSinceYMD> <FmtSinceYM>[à partir de|aux environs de|avant|après] MMMM yyyy</FmtSinceYM> <FmtSinceY>[à partir de|aux environs de|avant|après] yyyy</FmtSinceY> <FmtSinceMD>[à partir du|aux environs du|avant le|après le] d MMMM</FmtSinceMD> <FmtUntilYMD>[jusqu'au|jusqu'aux environs du|jusqu'avant le|jusqu'àprès le] d MMMM yyyy</FmtUntilYMD> <FmtUntilYM>[jusqu'en|jusqu'aux environs de|jusqu'avant|jusqu'après] MMMM yyyy</FmtUntilYM> <FmtUntilY>[jusqu'en|jusqu'aux environs de|jusqu'avant|jusqu'après] yyyy</FmtUntilY> <FmtUntilMD>[jusqu'en|jusqu'aux environs du|jusqu'avant|jusqu'àprès] d MMMM</FmtUntilMD> <FmtFromYMD>[du|d'environ du|d'avant le|d'après le] d MMMM yyyy</FmtFromYMD> <FmtFromYM>[de|d'environ|d'avant|d'après] MMMM yyyy</FmtFromYM> <FmtFromY>[de|d'environ|d'avant|d'après] yyyy</FmtFromY> <FmtFromMD>[du|d'environ du|d'avant le|d'après le] d MMMM</FmtFromMD> <FmtToYMD>[au|aux environs du|à avant le|à après le] d MMMM yyyy</FmtToYMD> <FmtToYM>[à|aux environs de|à avant|à après] MMMM yyyy</FmtToYM> <FmtToY>[à|aux environs de|à avant|à après] yyyy</FmtToY> <FmtToMD>[au|aux environs du|à avant le|à après le]d MMMM</FmtToMD> <FmtFromAndTo>{0} {1}</FmtFromAndTo> </FmtDateRange> Feel free to change if you wish. I reckon it's a bit weird sometimes, e.g. "à après le". Make sure the front and end tag match, e.g. <FmtToMD> and </FmtToMD>. I just changed MMM (short 3 letter month) into MMMM (full letter month). You may also change back if you want. Experiment and you'll see. Salut JC
|
By genome - Thursday, June 7, 2007
|
Yes a good point maru-san. It applies not just to countries part other parts of the address as well e.g. e.g. The White House is located in Pennsylvania Avenue but The White House is located at 1600 Pennsylvania Avenue
It would perhaps be easier if the address components were GenoPro Place objects instead of text fields, since then a place prefix would be available. But since the data does not properly support the current sentence construction it would be bettter to avoid the issue with a change in the phrase to say 'The address of 'The White House' is 1600 Pennsyvania Avenue etc. ' thus excluding prepositions. If a place category present it would become: 'The White House' is a domicile and the address is 1600 Pennsyvania Avenue etc.' I think I'll also change domicile to a place of residence as in my experience the word domicile tends only to be used in legal documents. You are correct JC, french is not one of my strong points. As I think I have said earlier, my french phrases were obtained using Google's translate tool. I'll replace the example in Dictionary.xml with your version.
|
By maru-san - Thursday, June 7, 2007
|
I actually had changed it this way in my German skin.
|
By jcguasp - Sunday, June 10, 2007
|
To Ron. A few more translation issues for you. A) Suggestions 1) PlacePrefix: In <PhPlaceDescription>,the preposition "in" (4 times) should be set/included within the PlaceCat param {3}, {4}, {5} and {7}, based on the Place Gender and/or on the PlacePrefix_.... Also "located" should be M or F, e.g. situé or située, based on param {1} gender. 2) MetaData may not be very important. Genopro to decide on the implementation: - <FmtMetaDescIndividual1> born -> should be in FR (né or née), based on {0} gender. - <FmtMetaDescIndividual2> named (twice) -> should be: prénommé, prénommés, prénommée or prénommées, based on the subject Inds genders and qty. B) Bugs (I think) 1) i.Session("NamePossessive") I lately noticed: Something's wrong. For info, in the underlines, i.Session("NamePossessive") = "de Jacquelinede ". This is with 2.0.0.5 DateFix and <PossessiveProperNoun T="(^[aeiouyh].*$)=d'$1.*$)=de $1:" /> in Dic. 2) <FmtDatesIndividual T=" ([b. {0} ][{!1} {2} ][d. {3} ][funeral. {4} ][burial. {4}])"/> in Dic. Shouln't the last param be {5}? Thank you JC
|
By rboshuis - Monday, June 11, 2007
|
Ron, When trying to do translations I come to the situation that in Dutch, sometimes sentences like Rons father can be better said as The father of Ron. You can imagine that that requires me to change the whole script since in stead of needing the processive noun, I need the normal noun. Also, I started to add links to wikipedia for places that are covered in wikipedia. However, the custom tags don't show up very well. Could we think about a solution there as well? For example adding some html with both the contents and the name of the tag, allowing one to easily add some custom data, in stead of changing either the contents (which I am doing now with <?html?> etc... (but that is really a huge and errorprone work (since I am talking about more than a 1000 places.)) Last but not least, the sentence "A custom tag is a generic placeholder to record additional information. You can customize those tags by using the Tag Editor from the Tools menu." does not seem to be part of the dictionary. Honestly I don't see why there is the extra level of hierarchy, but if it is intended and functional, it should be translatable. My two pennies.... :-) rgds, Ronald PS. 2.0.0.5 was already a big improvement both in functionality as well as in translatability.....
|
By El Matao - Monday, June 11, 2007
|
rboshuis, it's the same in Spanish, it's better said "The father of Miguel" than "Miguel's father" I've solved it changing PossessiveProperNoun to <PossessiveProperNoun T="(^.*$)=de $1:" /> also my PhParents could by <!-- 0=name's, 1=is|was, 2=html father name, 3=his|her, 4=is|was 5=html mother name --> <PhParents T="{  }{\U}[[{?2}el padre][{?!2^5}la madre] {!0}][ {!1} {2h}][{?5}[{?2} y {!3} madre] {!4} {5h}]]." /> Note that in Spain is normal not to change the last name of a women after the marriage a) father name = "Ho Sampson", mother name = "Ma Dalton", child name = "Ba Sampson'" (1=4=es (is), 3=su (his)) 0="de Ba" El padre de Ba es Ho Sampson y su madre es Ma Dalton. b) without mother name El padre de Ba es Ho Sampson. c) without father name La madre de Ba es Ma Dalton.
But, in fact I use this one, because in Spanish is ok to remove the subject if it is obvious (in this case "Ba Sampson") <!-- 0=name's, 1=is|was, 2=html father name, 3=his|her, 4=is|was 5=html mother name --> <PhParents T="{  }{\U}[{?2}su padre[ {!1} {2h}[[{?2} y {!3}] madre {!4} {5h}]]][{?!2}su madre {!4} {5h}]." />
a) Su padre es Ho Sampson y su madre es Ma Dalton. b) Su padre es Ho Sampson. c) Su madre es Ma Dalton. Perhaps it's possible to refine the case a), and if 1=3 then Sus padres {1} Ho Sampson y Ma Dalton but now we need the plural of 1 (or 3) are/were (son/fueron) hope it helps you Gerardo
|
By jcguasp - Tuesday, June 12, 2007
|
To Ron: Various bits to be translated (in bold) seen from within generated .htm files. The items are mainly associated with MetaData & divFrameset. I didn't include toc_tree.htm in this review. As it may not be a vital point, Genopro to decide on the implementation. However some text do appear on a search result window and such FR short phrase should grammatically be correct. The divFrameset may also be seen by Site Visitors. - In many files (contacts.htm, family-....htm, ...), within the divFrameset tag - title="Learn how to build your family tree" - In many files, the 2nd half of the <head><title> sub-tag: - In contacts.htm ... - Genealogy Occupancy/Contacts - In a family-....htm ... Family (Note: the word order should be, e.g. Famille de Daniel ...) - In heading.htm ... - Genealogy Research - In home.htm ... - Report Summary - In place & places.htm ... - Genealogy Places and Locations - In source & sources.htm ... - Genealogy Sources and Citations - In toc_contacts ... - Contact Index - In toc_families ... - Family Surname Search Index - In toc_individuals ... - Genealogy Names Search Index - In toc_pictures ... - Family Picture Album - In toc_places ... - Places and Locations - In toc_sources ... - Sources and Citations - In contacts.htm: - <meta http-equiv="Content-Language" content="fr"/> - In default.htm Many Ph to be translated: - <body> <p>This <b>genealogy report</b> is about ... It contains 35 individuals and 12 families, and also 3 Photos from the family tree. <li><a href='...'>Find the Pausey family and its 10 ancestors</a> (it should say "... la famille Pausey ...") <li><a href='...'>Search the Foud family and its 3 persons</a> <li><a href='...'>Find the Vittorio family and its 1 persons</a> <li><a href='...'>Search the Picmal family and its 1 people</a> <p>You may also search for the following family names: ... Download GenoPro from <a href="..." </body> - In gmap_place.htm, gmap_places.htm & popup.htm - the whole divFrameset - In heading.htm - <meta name="keywords" content="..., ReportHeaderGeneratedByGenoPro, ..." /> - <img src="images/genopro.logo.gif" title="Create Your Family Tree in Minutes!" alt="Create Your Family Tree in Minutes!" width=.../> (point already mentioned in post 18026) - ... alt="Contact the creator of this genealogy report"> (this item is from heading.htm template) - In home.htm - ... version 2.0.0.5 du 09 June 2007 avec la ... - In place.htm - <meta name="description" content="Family History, Ancestry, ..." /> - In popup.htm - the Lang content="fr" may be set - In toc_... - within the divFrameset, (GenoProReportFamilies), (GenoProReportIndividuals), (GenoProReportPictures), ... (i'm not sure if these ones have to be translated) - + "A custom tag ..." Ph requested by rboshuis in post 18036. Thank you Ron. JC
|
By El Matao - Wednesday, June 13, 2007
|
Ron. Another one "custom" in home.htm, it has no entry in Dictionary.xml Thanks Gerardo
|
By maru-san - Wednesday, June 13, 2007
|
Ron, can you please review also:
PhGodparents T="{ }{\U}{!0}[ godfather was[{?3}/is] {1}][[{?1} and {!0}] godmother was[{?3}/is] {2}]." / since the field is not limited to one person. I have a number of records where two or more are listed as godfather/godmother.
|
By genome - Thursday, June 14, 2007
|
Phew, quite a few things here to work on! I have a bit a spare time now so I'll get on with it and hope to have a revised version in a day or so. Some responses to the recent postings: Firstly JC, A 1) PlacePrefix I think this is answered in my earlier post. the address components are not GenoPro places so have no category or preposition. The solution I intend to use is to reword the phrase as indicated. a 2) Metadata. Agreed fix required. B 1) NamePossessive. Not sure what is happening here. Could you try changing <PossessiveProperNoun T="(^[aeiouyh].*$)=d'$1.*$)=de $1:" /> to <PossessiveProperNoun T="(^[aeiouyh].*$)=d'$1.+$)=de $1:" /> ? b 2) FmtDatesIndividual. Yes you are correct. I'll fix it, thanks
and Ronald, 1) PossessiveProperNoun. Does the Dictionary entry <PossessiveProperNoun T="(^.*$)=de $1:" /> solve your problem, as suggested by Gerardo and also used as a French example in the Dictionary? Or do you sometimes need the Dutch possessive form, 'Rons', and at other times 'de Ron'? 2) The 'custom markup' feature already allows a <?merge "some text ............" customtagname ?> format that can be used in the Place.Comment field. Also if you create custom tag called _Narrative this will be added after the Place description and can contain 'Custom Markup' tags. I will also change the code so that Place.Description can also contain 'Custom Markup'. See http://support.genopro.com/FindPost17355.aspx for more on Custom Markup. I did recently find a bug in the <?merge?> handling so you may want to wait for my next release before trying it out. 3) Custom Tag Layout Descriptions. The sentence you quote is the default Layout Description which can of course be changed using the Tag Editor. For this reason there is no need for a Dictionary translation. Indeed since the user can edit the text to anything he/she requires and also have more than one layout then Dictionary translation is impossible. I can see no reason why anyone would want to leave this default description in their report as it is completely meaningless in the context of a report. I would prefer that this default phrase was removed from GenoPro and the initial description left blank or perhaps set to "<Enter a description here>". I am considering adding another feature to Custom Markup so that text fields can contain more than one language version of the text and the version selected for the report will be that corresponding to the Skin language. The two levels. i.e. layouts and custom tag descriptions, allow custom tags to be categorised and grouped separately, using the layout description to describe the group, a very useful facility.
JC & Gerardo, I'll work through these suggestions.
and lastly, but not least, to maru-san PhGodparents. Since Godfather & Godmother are simple text fields I will alter the code to detect either a comma or ampersand in the text and then assume multiple godparents, passing a couple of boolean parameters to indicate more than one godfather or more than one godmother, and change 'is/was' accordingly.
|
By rboshuis - Thursday, June 14, 2007
|
1) Yes, I'd prefer to use sometimes Rons family and sometimes The father of Ron. But I'll try the latter and see the effect on the report and see if it doesn't too often have the ....of... of... of... etc. 2) and 3) I didn't know of their existence, I should be all set with these... rgds, Ronald
|
By jcguasp - Sunday, June 17, 2007
|
To Ron: One adjustment to do when a NameDic lookup is involved. Here it's about a place: The entry in my nameDic is <N EN="United Kingdom" FR="Royaume-Uni" FR_L=" au [Royaume-Uni]" /> The input in my .gno file is "United Kingdom". 1) Royaume Uni should be listed under the R letter in these indexes: 2) UK should be substituted by Royaume Uni within the Most popular places list: Hope I didn't forget any other loc, within the rep, for these substitutions. Thank you Ron, JC
|
By genome - Monday, June 18, 2007
|
Thanks once more JC, another couple of points that slipped through the net but thankfully not too difficult to put right. I have now posted the fourth update to my 2.0.0.6 release candidate. As usual this can be found in the first post of this thread. Hopefully I have corrected all the points raised since 2.0.0.6RC3, but if I have overlooked any please don't hestitate to prompt me via this thread or a PM via this forum. Update: I forgot to mention that the changelog.txt file for 2.0.0.6RC4 has two sections. Section 1 details changes between 2.0.0.5 and 2.0.0.6RC3 and Section 2 documents changes between 2.0.0.6RC3 and 2.0.0.6RC4. Therefore if you have already made a translation based on RC3 you only need to view Section 2.
|
By jcguasp - Thursday, June 21, 2007
|
To Ron: A few more issues related to translation or to the rep itself. A) Translations 1- Report.WriteFormatted Dic("FmtHtmlHomeSkin") in home.htm - It would be better if & " ", after Dic("Custom"), could be removed. The space can easily be provided within the template. - Is there a way to change/customize the version date at the very end of the ph, i.e. D, M & Y: Ce rapport généalogique a été généré par GenoPro® version 2.0.0.5 du 20.6.2007 avec la matrice de traduction personnalisée Rapport narratif français version 2007.06.18. For info, I manually changed the params order for the middle date (20.6.2007). However it would be good, generally speaking, if all dates could automatically match the template <FmtDateSort> in dic. B) Bugs, adjustment or additions 1- <PhPlaceDescription> in dic The Ph doesn't seem to be working as there's no narrative in the report. 2- Sub WriteHtmlRelationships(i) in util.vbs The enum (2 ways SR) shows: "Roommate", "LivesWith", "Neighbor", "Acquaintance" I think the following should also be added: "Associate", "Know", "Relative" and "WorkWith" By the way, as already mentioned in a previous post, what is the difference in-between Acquaintance and Know? 3- Place Index alpha sorting - Despite the place name substitution via NameDic, my place "Royaume-Uni" (United Kingdom in EN) is not alpha sorted in the Place Index: 4- my post 17791 dated 20/5 (error message) has not been implemented yet. 5- my post 17793 dated 20/5 (adopted/fostered child Ph order and missing siblings) has not been implemented yet. 6- <<FmtMetaDescIndividual2> It seems that param {2} always default to <_Spouse>, ignoring ends _M or _F. I cannot get any Fem word in the meta Desc Nar Ph. Please check the routine. 7- Few bits & pieces not written to generated .htm files. I May be wrong or the var may be = "" though. - FmtCopyright in default.htm - <meta name="description" content="??" in place.htm - "Content-Language" content="fr" in popup.htm - strTitle from @[ Report.WriteText strTitle ]@ in source.htm - svghelp.htm: shouln't everything (<Title> and text) be in Dic? 8- Minor cosmetic corrections (incl. some words from comments) - from PLaces.SortBy("Name") to Places.SortBy("Name") in places.htm - from preposiiton to preposition in util.vbs line 40 - from shown on on to shown on in config line 37 - from identivier to identifier in dic line 478 - <PossessiveProperNoun> (for update purpose) from T="(^[aeiouyh].*$)=d'$1'.*$)=de $1:" to T="(^[aeiouyh].*$)=d'$1.+$)=de $1:" in dic line 625 (the 1st version didn't work, even with the 2nd ' removed) - from pupose to purpose in namedic line 3 - from atribute to attribute in namedic line 12 9- Is it possible to capitalize the 1st letter of the Ph appearing in Timelines bubbles? I tried to add up {\U} in the templates but it shows 4 square chars! 10- It would be useful to have the NameDic lookup substitution extended beyond the places, i.e. for occupations, cause of death (specify), picture name, source subtitle, brief source description, citation ref., text quoted from source and the many comments. Plenty fields then! Finally, could you remind me/us how to avoid the appearance of this in a rep: Thank you Ron and good work, JC
|
By genome - Saturday, June 23, 2007
|
Thanks JC, I have now posted version 2.0.0.6RC5, hopefully a step or two closer to a 'final' version. Some items I've fixed others I have commented on below. The ChangeLog.txt file has a Section 3 detailing changes to the Dictionary between RC4 and RC5. A. 1. 'Custom' in FmtHomeSkin. an extra space is needed when 'custom' is added. I have left 'as is' as a 'formatted string' rather than a 'phrase' because of the problems adding html codes to Dictionary 'phrases'. A 'formatted string' does not have conditional subphrases and so the extra space cannot be handled in the phrase. Your '2007.06.18' is the 'SkinVersion' taken from Config.xml. It just so happens it is expressed as a date, but need not be. I tend to prefer dates in the format yyyy.mm.dd to avoid confusion with the american format mm.dd.yyyy and the British (& European?) format of dd.mm.yyyy in dates such as 12/04/2007 which could be 04/12/2007 depending on which side the 'pond' you live. If you want to change the Skin version format I suggest you amend config.xml. FmtDateSort is purely for formatting dates prior to sorting and so is not appropriate here.
B. 1. Thanks, I have corrected it now. Note that the Place description is no longer part of the phrase as it is now handled in the code. 2. Again code amended. My interpretation of an acqaintance is someone you know reasonably well, i.e. you have a proper conversation with them. The Internet Dictionaries suggest someone less intimate than a friend. Whereas 'knowing' someone is a weaker relationship, perhaps you know their name and only exchange an ocassional greeting. There is a English expression 'nodding acquaintance' meaning you just acknowledge each other say in the street. 3. Code fixed 4. I had overlooked this one, so thanks for the prompt, code should be OK now. 5. I have amended the phrase to add the space before 'through'. As regards reorganisation of the rest of the phrase, this requires a little more effort so I'll leave it untill 2.0.0.7. Also I believe there is a problem with GenoPro's interpretation of half siblings. My view is that half siblings are biologically related via a single parent, and so adopted/fostered siblings should not be included. 6. Code amended to take account of gender of mate(s). 7. All sorted. I think strTitle in source.htm was redundant so I have deleted it. 8. All fixed. 9. I have fixed using Util.StrFirstCharUCase 10. I prefer to extend 'Custom markup' to handle these translations rather than using ther NameDictionary. These are mostly unique strings appearing once in the .gno file. I am considering allowing for conditional text formats e.g. [{?en}engineer][{?fr}ingénieur] in these fields. The Narrative skin would then select the required version.
And finally, you can prevent Custom Tags from appearing in the Additional Items section of a report by using the Tag Editor to place them in a Custom Tag Dialog Layout with a description starting with an underscore (_) or give the Tag itself a description starting with underscore. The Dictionary-defined 'Private' string can be used in place of an underscore. Also remember that you can, and should, change the default Custom Tag Layout Description, ' A custom tag is a generic placeholder....' to something more suitable.
|
By jcguasp - Monday, June 25, 2007
|
To Ron: Here's a few more suggestions. As you said, it's coming to an end as I'm quite happy with the result. I think now you may/will have more requests from other language users. Also waiting for the trans implementation of occu, ... A) Translations 1) The Fem gender doesn't work (was OK before):
Note: it's OK when <fHideFamilyDetails = "N"/> B) Bugs, corrections & additions 1) with the param <fHideFamilyDetails="N"> in config.xml, the said param cannot be changed within the config setting panel prior to generate a report. I got this for one of my Ind (after selecting yes in the panel): Clicking on the red ul "Unknown", I got this: Strange! For info, I didn't try changing the other params. I don't know if they're working or not? 2) Generated Place.htm - I think a space should be removed in-between ancêtres and à: <meta name="description" content="Historique de famille et ancêtres à Glasgow" /> - a lookup substitution should also be implemented: <meta name="keywords" content="Lieu United Kingdom" /> 3) <FmtMetaDescIndividual1> A NameDic look up should be implemented, as shown in one of my generated Ind.htm (b.Place): <meta name="description" content="Rapport ancestral de Martine Bronca, fille de ..., née le 18 octobre 1948 à United Kingdom. Martine a un époux/partenaire nommé ..." /> 4) <PhUnion> A check-up routine, similar to GodFathers and Godmothers, should be implemented, for multiple witnesses. I added a param {9} in Lang.vbs and it's working. This extra param {9} will simply be ignored in an EN report: ' The family has at least one union/marriage g_RegEx.Pattern = "[,&]" For Each m In collUnions Report.WritePhraseDic "PhUnion", ..., strAlso, g_RegEx.Test(m.Witnesses) ... For info, in FR, "witnessed by ..." is "le témoin était ..." or "les témoins étaient ..." Note: I also suggest Genopro to implement a message system when the cursor is in some field with an input particularity. In our case, the Witnesses field message could say, e.g. "Use ',' or '&' for delimiters in-between names". This message could pop up in the following red rectangle area: or in a bubble. 5) 1st letter capitalization of the Phrases appearing in Timelines bubbles? It's OK now for the 1st Ph but not yet for the subsequent Ph, e.g.She was born ... . she died ... 6) my post 17791 (error message) has been implemented but only for the ERs. For the SRs, the message still pops up. 7) my post 17793 (adopted/fostered child) has been partly implemented. That's OK. In addition, a space before "through" should also be added in <PhPL_foster>. 8) Google message For info, the place substitution is not done on United Kingdom when input as a Country. Also on clicking on "Afficher la carte Google ...", the message is not 100% Unicode compatible. The red ul should be '. Thank you Ron. JC
|
By GenoProSupport - Monday, June 25, 2007
|
jcguasp (6/25/2007) Note: I also suggest Genopro to implement a message system when the cursor is in some field with an input particularity. In our case, the Witnesses field message could say, e.g. "Use ',' or '&' for delimiters in-between names". This message could pop up in the following red square area: or in a bubble. This is a Great idea. That space could be used to display additional information, tips or some extra help regarding the control having the focus. I am wrapping up the multi-lingual version, and later plan to add "tips" for each control. This way, the user won't have to read the user's manual to discover hidden features of GenoPro.
|
By genome - Tuesday, June 26, 2007
|
jcguasp (6/25/2007) Here's a few more suggestions. As you said, it's coming to an end as I'm quite happy with the result. I think now you may/will have more requests from other language users. Also waiting for the trans implementation of occu, ...So, close but not quite close enough yet!. There are some new errors here but also some elementary slips on my part. I have posted another attempt at the 2.0.0.6 skin in the first post of this thread. (RC6) Update: This version is now availlable in GenoPro 2.0.0.6 download I have also included as a bonus the optional translation of Occupation Titles. But this bonus comes at a price. I have changed the format of NameDictionary so that all attributes relating to Places should now be prefixed with 'P.' and attributes relating to Occupation Titles must be prefixed with 'O.' The NameDictionary.xml file included with the skin has examples of each. This is to avoid confusion when surnames are the same as places and occupations, e.g. London, England, Baker, Plumber etc. Whilst you may want to translate places and occupations you do not necessarily want to translate surnames as well. Similar to Place translation, the Config.xml Parameter LangOccupation specifies the language code for Occupation Titles in the .gno file when they are to be translated to the skin language.
|
|