GenoPro Home
GenoPro Home  |  Get Started With My Genealogy Tree  |  Buy  |  Login  |  Privacy  |  Search  |  Site Map
 

GenoPro Support Forum




Updates to Report Skin Templates since GenoPro 2020 version 3.1.0.1

Click to view RSS...
Author Updated 2020.08.08
Posted Tuesday, July 7, 2020 - Post #40608
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1

Last Login: 55 minutes ago
Posts: 2,941, Visits: 21,544
This cumulative skins update containing all skins updates made since the release of GenoPro 2020 version 3.1.0.1 

It has a large number of additional changes and so will possibly contain an error or two.  Please report any issues you discover and I will do my best to correct them.

Scripts for all reports are now held in the Common\Code folder.  This approach allows the various translations of some skins to invoke the same scripts rather than their own, possibly outdated, copy.  

In order to 'trick'  GenoPro into using this Code folder each skin folder has a dummy Code folder containing a single file placeholder.txt (needed as I believe the GenoPro installer is not happy with empty folders).  The skins have a 'bootstrap' .vbs/VBScript or .js/JScript  file that runs first in Config.xml and on the first run of that skin the script replaces the dummy Code folder with a Junction (aka Reparse Point) linking to the Common\Code folder.  The skin then runs normally. 

Messages relating to this 'bootstrap process are held in folder Common\Boot in files ConfigMsgXX.xml, where XX is language code. 

Translations of configuration messages are held in the skin folder as ConfigMsgLocal.xml or in some cases Config.xml.  These messages will replace the base English messages held in Common\Code\reportname\ConfigMsgBase.xml

I have reformatted some of the translated Dictionary.xml files via my ReformatXML utility (see App Launcher skin) to allow easier side by side comparison and editing against the English version (e.g.using WinMerge) .  I have  attempted translations to some of the Dictionary.xml files where messages were missing.

I recommend that you create a new GenoPro Report Skins folder and download and unzip the attached file into that folder.  You can then direct GenoPro to use this new folder under the Options tab the the Tools/Generate Report dialogue.  This will allow simple regression to previous versions of the skins should you deem it necessary, i.e. if I've got something wrong!



'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"


Skins 2020.08.08.zip (7 views, 3.85 MB)

Tags:

Edited: Yesterday @ 1:11 AM by genome
Posted Yesterday @ 1:14 AM - Post #40699
Legendary Master

Legendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary MasterLegendary Master

Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1

Last Login: 55 minutes ago
Posts: 2,941, Visits: 21,544
The first post in this thread has been updated once more with revised Report Skin templates, 

Skins 2020.08.08 includes the following changes:

Updates to {DE} & {NL-BE} skins as provided by albertsali & Nand respectively

previous revisions included:

Prompt added to Kinship Calculator (and its translations) via Configuration Parameters setting to exclude searching for in-law relationships because at the present time this is unreliable and can produce false reports.  Also changes to ensure sons/daughters nephews/nieces are labelled on report.  Changes to {DE} Dictionary.xml as posted by albertsali but with modification for the above.

Fix to all Ahnentafel and Ancestors Reports to ensure proper reporting of ancestors above the maximum given in ParentsAncestors tag

Fixes for other issues reported in thread http://support.genopro.com/Topic40641.aspx up to the date and time of this post.

All Ahnentafel and Ancestors Reports now name the output html file using the individuals name as per the Narrative Report. i.e. lastname-firstandmiddlename-id.htm. This makes things easier when producing reports for several individuals as the previous output does not need to be renamed or moved.

Also in the above  reports an optional Dictionary tag ParentsAncestors allows specific names for each generation.e.g.:
he German Ahnentafel Report we have: 
<!-- P = default phrase when level > max value,  T = "max, offset"
where max= max x in Cx attributes,  offset = offset to level for 'times' in default phrase
e.g. if level=25 and max=23 and offset=2 phrase is [level - offset] x {P} i.e. 23 x Ur-Großeltern -->
<ParentsAncestors
C1="Eltern"
C2="Großeltern" 
C3="Ur-Großeltern"
C4="Urur-Großeltern (Alteltern)"
C5="3 x Ur-Großeltern (Altgroßeltern)"
C6="4 x Ur-Großeltern (Alturgroßeltern)"

                        etc.

C22="20 x Ur-Großeltern (Erzahneneltern)"
C23="21 x Ur-Großeltern (Erzahnen-Großeltern)"
C24="22 x Ur-Großeltern (Erzahnen-Urgroßeltern)"
P="Ur-Großeltern"
T="24,2"
V="2020.07.19+"/>


{DE} Verwandtschaft has Dictionary.xml updates.

fix an issue with the Narrative Report whereby on change of theme images do not appear to be updated to the correct theme. 

a translation of {EN} Export to Gedom into German by albertsali has been added - {DE} Export nach Gedcom

If you have any comments or find any issues please report these at http://support.genopro.com/Topic40641.aspx


'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"


Similar Topics

Click to view RSS...
Expand / Collapse

Reading This Topic

Expand / Collapse