Prev
German Umlaute - Categorized in: 
Report a Problem
5 posts.
Started 18 Dec 2013 by willybald12. Latest reply 19 Dec 2013 by lkessler.
RSS
German Umlaute - Categorized in:
5 posts. Started 18 Dec 2013 by willybald12. Latest reply 19 Dec 2013 by lkessler. RSS
Leave your Reply
You must login to post your reply.
Joined: Wed, 18 Dec 2013
0 blog comments, 2 forum posts
Posted: Wed, 18 Dec 2013
I am working with a trial version of Behold with the translation table german.bho,
with a Swiss-german setting for Keyboard and langage.
I import a gedcom file from Legacy 8.0 as follows:
Behold version: 1.0.5.1, 26 Mai 2013
Registered to: Willy Schwarz
Log created: 18.12.2013 15:48:13
Reading file: ........Schwarz100920.ged
Last modified: 18.12.2013 15:46:41
File size: 148 KB (152'046 bytes)
File Byte Order Mark: EF BB BF (UTF-8)
----------------------
Listing of Input Messages
1245: 2 DATE 1623-1624
** Behold will change this to a date phrase by adding parenthesis.(#1): This date does not conform to GEDCOM standards.
----------------------
GEDCOM Header Information
SOUR: Legacy
SOUR.VERS: 8.0
DEST: Legacy
DATE: Wed 18 Dec 2013
GEDC.VERS: 5.5.1
GEDC.FORM: LINEAGE-LINKED
CHAR: UTF-8
----------------------
Summary of GEDCOM Tags
Records: 779
FAM 106
HEAD 1
INDI 384
NOTE 205
SUBM 1
................................................................................................
Now the German Umlaute are not shown correct e.g
Einb�rgerung
ä, ö, ü show the same sign, also the French letters.
I tried with conversion to UTF16 without any improvement.
How can I correct this problem.
Thanks
Joined: Sun, 9 Mar 2003
288 blog comments, 245 forum posts
Posted: Wed, 18 Dec 2013
From what I understand, Legacy doesn't support Unicode. According to an article on Legacy 7 by Tamura Jones: "Legacy is still a codepage-based design. Legacy does still not support Unicode, and that automatically limits its support for other characters sets. Legacy will export to and import from ANSEL and UTF-8, but it will only export or import characters that happen to be in Window ANSI. It claims to support import from ANSEL and UTF-8, but its import ability for those encodings is limited to the 256 characters in Windows ANSI." From what I can read about Legacy 8's improvements, I don't think they fixed that.
Please take a look at your GEDCOM file and load it into a reader that support Unicode, such as Wordpad which is included in every Windows computer. See if you can see the umlauts and other special characters in the GEDCOM file. If you cannot, then the problem is Legacy's export and I can't fix that.
But if you do see the characters, then I'd really appreciate it if you wouldn't mind sending me your GEDCOM so that I could see why Behold's not working properly with it. My email is at the bottom of the forum page.
Louis
Joined: Sun, 9 Mar 2003
288 blog comments, 245 forum posts
Posted: Wed, 18 Dec 2013
There is one other possibility. It could be a bug discovered a few months ago. See: UTF-8 with BOM does not display right.
If that is the problem, then until I issue the next version, you'll have to save your UTF-8 file which your listing above shows that you have a Byte Order Mark (BOM), and save it without a BOM. You'll need a special editor to do that. I can do that for you if you need it done.
Louis
Joined: Wed, 18 Dec 2013
0 blog comments, 2 forum posts
Posted: Thu, 19 Dec 2013
Dear Louis
Thank you for your replay.
I think I did find a solution for my problem. When I export the GEDCOM file from Legacy8 in setting ANSI all the umlauts will appear in the Behold file!
The next step now is to create an output file the way I prefer and exporting it to rtf.
It seems Behold is very capable for this.
What I especially like in Behold is the tree form of the families in the overview.
Willy Schwarz
Here part of the log:
***************************************************************************
Behold version: 1.0.5.1, 26 Mai 2013
Registered to: Willy Schwarz
Log created: 19.12.2013 15:06:03
Reading file: ..........\Schwarz100920Leg-ANSI.ged
Last modified: 19.12.2013 15:05:10
File size: 148 KB (151'678 bytes)
File Byte Order Mark: none
----------------------
Listing of Input Messages
1245: 2 DATE 1623-1624
** Behold will change this to a date phrase by adding parenthesis.(#1): This date does not conform to GEDCOM standards.
----------------------
GEDCOM Header Information
SOUR: Legacy
SOUR.VERS: 8.0
DEST: Legacy
DATE: Thu 19 Dec 2013
GEDC.VERS: 5.5.1
GEDC.FORM: LINEAGE-LINKED
CHAR: ANSI
******************************************************************************
Joined: Sun, 9 Mar 2003
288 blog comments, 245 forum posts
Posted: Thu, 19 Dec 2013
I'm glad that solved it for you, Willy. Hopefully you'll find Behold useful. More great things coming soon.
Louis