|
|
|
|
Customers
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: Thursday, March 6, 2025
Posts: 84,
Visits: 288
|
Ah. I see the point about nr 3, that it needs gender in certain languages...
And I understand that we don't get the same output from the generator.
I am retranslating the whole report dictionary atm, to have a fully working translation hopefully at the time you release the next english skin, hence my many questions. I love the phrase testing possibilities now built-in in GenoPro itself: it reduces the time needed for checking and rechecking results so much I could hardly believe it!
My "odd" results when running the report generator may in a few cases be the result of how padding spaces slip in or away in the data itself, and I sometimes wonder why a space is, or isn't, entered in the "test" syntax; I will make sure I have correct data before changing the report dictionary syntax itself in the skin.
But this again brings up my earlier issue with padding: Is there now an alternative for removing trailing blanks from names and other "free text" fields automatically? Most of my flaws in the report "back in those days" were extra blanks after names, that were in the data. Has this been addressed?
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 1 hour ago
Posts: 3,408,
Visits: 26,281
|
Anna (8/15/2008)
1) Original ph: <PhBurial T="{  }{\U}{!0} {1!=burial was}{2}{3h}."
<PhBurialTxt T="{!0} {1!=burial was}{2}{3}." /> This phrase drops the word "was". Sorry, Anna I don't see your point here. {1} is the enumerated 'dispositon type', so {1!burial was} evaluates to either the disposition type enumeration (i.e. from Dictionary <BodyDispostion> section or the default text 'burial was' if there is no DispositionType set. My tests show this is working correctly, i.e. 'burial was' is inserted when there is no disposition type.2) contact details is cluttered, added spaces, and removed the "-" after details: <PhContact T="{  }{\U}[{?!5}[{?4}{!4} kontaktinfo: ]][ Telefon: {0} ][ Mobil: {6} ][ Fax: {1} ][ E-post: {2h} ][ Websida: {3h}]."/> (summary ph is good) 3) <PhDivorce T="{  }{?0}Deras äktenskap [{?1}was][{?!1}{1=was}] upphävdes][{?!0}[{?1|2|3|5|6|7}De skildes ]]{1} {2h}[ {4h} ][, makens jurist var {5h}][[{?5} och][{?!5},] makans jurist var {6h}].[ Den genomfördes av {7h}.]" /> <PhDivorceTxt T="[{?0}Deras äktenskap [{?1}was][{?!1}{1=was}] upphävdes][{?!0}[{?1|2|3|5|6|7}De skildes ]]{1}{2}[ {4}][, makens jurist var {5}][[{?5} och][{?!5},] makans jurist var {6}].[ Den genomfördes av {7}.]" /> Here there is need for the extra space between {1} and {2h} (yellow), and the argument 3 is never used.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Customers
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: Thursday, March 6, 2025
Posts: 84,
Visits: 288
|
1) Original ph: <PhBurial T="{  }{\U}{!0} {1!=burial was}{2}{3h}."
<PhBurialTxt T="{!0} {1!=burial was}{2}{3}." /> This phrase drops the word "was". 2) contact details is cluttered, added spaces, and removed the "-" after details: <PhContact T="{  }{\U}[{?!5}[{?4}{!4} kontaktinfo: ]][ Telefon: {0} ][ Mobil: {6} ][ Fax: {1} ][ E-post: {2h} ][ Websida: {3h}]."/> (summary ph is good) 3) <PhDivorce T="{  }{?0}Deras äktenskap [{?1}was][{?!1}{1=was}] upphävdes][{?!0}[{?1|2|3|5|6|7}De skildes ]]{1} {2h}[ {4h} ][, makens jurist var {5h}][[{?5} och][{?!5},] makans jurist var {6h}].[ Den genomfördes av {7h}.]" />
<PhDivorceTxt T="[{?0}Deras äktenskap [{?1}was][{?!1}{1=was}] upphävdes][{?!0}[{?1|2|3|5|6|7}De skildes ]]{1}{2}[ {4}][, makens jurist var {5}][[{?5} och][{?!5},] makans jurist var {6}].[ Den genomfördes av {7}.]" />
Here there is need for the extra space between {1} and {2h} (yellow), and the argument 3 is never used.
|