|
By Nand - Monday, December 9, 2013
|
Tested with:
GenoPro 2.5.4.1
English Narrative Report 2013.08.12
Flemish Narrative Report 2013.08.12
-----------------
Issue #1
The "Family Pictures" label as seen at the top in the image above is easy to translate since it is defined by a single tag <HeadingPicturesFamily> in the dictionary.
The "Family Picture Notes" label at the bottom is a different story. "Family" is defined in the <Family> tag and "Picture Notes" in the <FmtAnnotationPicture> tag. Moreover, upon concatenation, a space is inserted between the two strings.
As current work-around, I defined an empty string as T attribute in the <Family> tag but of course this has a side effect. If the <Family> tag is used elsewere in the report, that translation will fall back to the default English text.
Suggestion 1: Provide a single tag to define the "Family Picture Notes" label below the picture.
Suggestion 2 (better): Drop the <Family> tag altogether and only keep the <FmtAnnotationPicture> tag (or even use the <AnnotationPicture> tag for this). Note: By the way, do we really need the "page last modified" at the bottom of each and every page? The home page already shows the last update and that is OK for me.
-----------------
Issue #2
The label "Picture Notes" is defined by the <AnnotationPicture> tag. Once again, easy to translate.
But the "Picture References" label is a combination of the <Picture> tag and the <PhReferences> tag, combined after inserting a space.
In Dutch (and in German) we only use a single "put together" word for this, where all words and letters are subsequent and no spaces inserted.
Suggestion: Provide a single tag to define the "Picture References" label. And, by the way, why not simply replace "Picture Notes" by "Notes" and "Picture References" by "References". We are in a picture section anyway.
Thanks for looking into this.
Regards,
Nand
|
|
By genome - Thursday, December 12, 2013
|
Hi Nand,I will sort something out for these translation issues in the next revision using your suggestions. I'd like ensure backwards compatibility to avoid disrupting existing translations. I think this can be achieved here. The page timestamp works differently on familytrees.genopro.com. GenoPro uses GenoProCache.xml to record MD5 checksums and timestamps of all files and when a report is regenerated in the same folder checksums are compared and if the file has not changed it is not uploaded, saving time. So in this case the timestamp does reflect when the page content or html was last changed. It is a pity that GenoPro does not appear to apply this technique to other FTP sites. I will provide another Config setting to suppress this feature of the report.
|
|