[LegacyUG] Creating gedcom for Export - UTF8 doesn't work properly

[EMB]

Again, a question. Version 8.0.0.595. Maybe more for the German list.

I created a gedcom file: gedcom 5.5.1 UTF8 and uploaded it via filezilla 
(forced UTF8) to a TNG-Website ( German UTF8). All the "Umlaute" 
(*umlaut* is the name of the two small dots above the letters A, O, and 
U in__German .) were 
wrong. (like


Rüdiger-).

Before I used creating a gedcom 5.5.1 and ANSI. There everything was 
correct. But I wanted to change to UTF8. What do I do wrong again? Or 
does it not work in Legacy?


Maybe one of you knows how to do properly.

Regards,

Eva B.


-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Creating gedcom for Export - UTF8 doesn't work properly

[Chris Hill]

Hi Eva

One immediate thought is whether you running a UK or USA language settings in 
Windows – I guess from one of your earlier messages that you may be German 
based. In theory, that should not cause any issues but I have had problems like 
that in the past.

I am UK based and therefore running on the ‘default’ Windows settings. From my 
tree, I have exported, as GEDCOM 5.5.1 using ANSI and UTF8 and have got the 
following address line (extracted from the GEDCOM file using Notepad++)

2 PLAC Norrköping, , Östergötlands län, Sweden

When I export it as ANSEL I get

2 PLAC Norrkèoping, , èOstergèotlands lèan, Sweden

which is what I would have expected.

 

Looking at the files in Notepad++, it is reporting the ANSI and ANSEL versions 
as being ANSI coded and the UTF as being UTF-8-BOM, so I presume that the 
system or Legacy has placed the Unicode header at the start of the file. I 
would need to do some testing and programming to prove that. 

Your example suggests that Rüdiger consists of upper case R, upper case A with 
tilde and then a One Quarter – in Unicode hex these are U-0052, U-00C3 and 
U-00BC according to Character Map on Arial. I guess that the ¼ should be ë 
(U-00EB), not sure about the case of the Ã. What I am not sure about is whether 
the German? based system uses different codings, which used be a problem 20-30 
years ago, but should not now.

I think my first question would be to view the text file, using Notepad or 
Notepad++, to ensure that the format is correct. If that says it is wrong, then 
there is a question about Legacy. If the text file is good, then the problem is 
between Filezilla and the TNG site. Again, I have seen issues with FTP systems 
getting data conversions wrong, especially if there are multiple versions of 
UTF and different implementations.

 

Regards

Chris

From: LegacyUserGroup [mailto:legacyusergroup-boun...@legacyusers.com] On 
Behalf Of EMB
Sent: 08 April 2017 13:07
To: Legacy User Group ; 
legacy-deutsch-ow...@legacyusers.com
Subject: [LegacyUG] Creating gedcom for Export - UTF8 doesn't work properly

 

Again, a question. Version 8.0.0.595. Maybe more for the German list.

I created a gedcom file: gedcom 5.5.1 UTF8 and uploaded it via filezilla 
(forced UTF8) to a TNG-Website ( German UTF8). All the "Umlaute" (umlaut is the 
name of the two small dots above the letters A, O, and U in German 
<https://simple.wikipedia.org/wiki/German_language> .) were wrong. (like 

Rüdiger-).

Before I used creating a gedcom 5.5.1 and ANSI. There everything was correct. 
But I wanted to change to UTF8. What do I do wrong again? Or does it not work 
in Legacy?

Maybe one of you knows how to do properly.

Regards,

Eva B.

 

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Creating gedcom for Export - UTF8 doesn't work properly

[EMB]

Hi, Chris,

yes, I'm German based and it seems to be a problem between filezilla and 
TNG.


I was looking at the files in Notepad++ and evereything was correct. So 
I have to find out what's between filezilla and TNG.


Thank you again for your help.

Regards,

Eva


Am 08.04.2017 um 15:36 schrieb Chris Hill:


Hi Eva

One immediate thought is whether you running a UK or USA language 
settings in Windows – I guess from one of your earlier messages that 
you may be German based. In theory, that should not cause any issues 
but I have had problems like that in the past.


I am UK based and therefore running on the ‘default’ Windows settings. 
From my tree, I have exported, as GEDCOM 5.5.1 using ANSI and UTF8 and 
have got the following address line (extracted from the GEDCOM file 
using Notepad++)


2 PLAC Norrköping, , Östergötlands län, Sweden

When I export it as ANSEL I get

2 PLAC Norrkèoping, , èOstergèotlands lèan, Sweden

which is what I would have expected.

Looking at the files in Notepad++, it is reporting the ANSI and ANSEL 
versions as being ANSI coded and the UTF as being UTF-8-BOM, so I 
presume that the system or Legacy has placed the Unicode header at the 
start of the file. I would need to do some testing and programming to 
prove that.


Your example suggests that Rüdiger consists of upper case R, upper 
case A with tilde and then a One Quarter – in Unicode hex these are 
U-0052, U-00C3 and U-00BC according to Character Map on Arial. I guess 
that the ¼ should be ë (U-00EB), not sure about the case of the Ã. 
What I am not sure about is whether the German? based system uses 
different codings, which used be a problem 20-30 years ago, but should 
not now.**


I think my first question would be to view the text file, using 
Notepad or Notepad++, to ensure that the format is correct. If that 
says it is wrong, then there is a question about Legacy. If the text 
file is good, then the problem is between Filezilla and the TNG site. 
Again, I have seen issues with FTP systems getting data conversions 
wrong, especially if there are multiple versions of UTF and different 
implementations.


Regards

Chris

*From:*LegacyUserGroup 
[mailto:legacyusergroup-boun...@legacyusers.com] *On Behalf Of *EMB

*Sent:* 08 April 2017 13:07
*To:* Legacy User Group ; 
legacy-deutsch-ow...@legacyusers.com
*Subject:* [LegacyUG] Creating gedcom for Export - UTF8 doesn't work 
properly


Again, a question. Version 8.0.0.595. Maybe more for the German list.

I created a gedcom file: gedcom 5.5.1 UTF8 and uploaded it via 
filezilla (forced UTF8) to a TNG-Website ( German UTF8). All the 
"Umlaute" (*umlaut* is the name of the two small dots above the 
letters A, O, and U in__German 
<https://simple.wikipedia.org/wiki/German_language>.) were wrong. (like


Rüdiger-).

Before I used creating a gedcom 5.5.1 and ANSI. There everything was 
correct. But I wanted to change to UTF8. What do I do wrong again? Or 
does it not work in Legacy?


Maybe one of you knows how to do properly.

Regards,

Eva B.





-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Creating gedcom for Export - UTF8 doesn't work properly

[Ward Walker]

I would recommend UTF-8. I would also suggest that you use ‘Legacy’ as the 
Gedcom target, not Gedcom 5.5. Otherwise, your parent-child relationship 
statuses will not be transferred to TNG. You might want to use the Customize 
option to exclude unwanted codes that show up in TNG, such as _UID and _TODO.

   Ward

From: EMB 
Sent: Saturday, 8 April, 2017 8:06 AM
To: Legacy User Group ; legacy-deutsch-ow...@legacyusers.com 
Subject: [LegacyUG] Creating gedcom for Export - UTF8 doesn't work properly

Again, a question. Version 8.0.0.595. Maybe more for the German list.

I created a gedcom file: gedcom 5.5.1 UTF8 and uploaded it via filezilla 
(forced UTF8) to a TNG-Website ( German UTF8). All the "Umlaute" (umlaut is the 
name of the two small dots above the letters A, O, and U in German.) were 
wrong. (like 

Rüdiger-).

Before I used creating a gedcom 5.5.1 and ANSI. There everything was correct. 
But I wanted to change to UTF8. What do I do wrong again? Or does it not work 
in Legacy?

Maybe one of you knows how to do properly.

Regards,

Eva B.

-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Re: [LegacyUG] Creating gedcom for Export - UTF8 doesn't work properly

[Ian Macaulay]

Ward:   Did you manage to get photos to link in TNG?I have yet to get
the linked photos to show up.

Ian

On Sat, Apr 8, 2017 at 3:04 PM, Ward Walker  wrote:

> I would recommend UTF-8. I would also suggest that you use ‘Legacy’ as the
> Gedcom target, not Gedcom 5.5. Otherwise, your parent-child relationship
> statuses will not be transferred to TNG. You might want to use the
> Customize option to exclude unwanted codes that show up in TNG, such as
> _UID and _TODO.
>
>Ward
>
> *From:* EMB
> *Sent:* Saturday, 8 April, 2017 8:06 AM
> *To:* Legacy User Group ; legacy-deutsch-ow...@legacyusers.com
> *Subject:* [LegacyUG] Creating gedcom for Export - UTF8 doesn't work
> properly
>
>
> Again, a question. Version 8.0.0.595. Maybe more for the German list.
>
> I created a gedcom file: gedcom 5.5.1 UTF8 and uploaded it via filezilla
> (forced UTF8) to a TNG-Website ( German UTF8). All the "Umlaute" (*umlaut*
> is the name of the two small dots above the letters A, O, and U in German
> <https://simple.wikipedia.org/wiki/German_language>.) were wrong. (like
>
> Rüdiger-).
>
> Before I used creating a gedcom 5.5.1 and ANSI. There everything was
> correct. But I wanted to change to UTF8. What do I do wrong again? Or does
> it not work in Legacy?
>
> Maybe one of you knows how to do properly.
>
> Regards,
>
> Eva B.
>
> --
>
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> To manage your subscription and unsubscribe http://legacyusers.com/
> mailman/listinfo/legacyusergroup_legacyusers.com
> Archives at:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>
>


-- 
  ICMac Sales: Hobby consultant (1986r.)
Office hours:   10:00 Am - 5:00 PM  most days
  Macaulay Genealogy
 Family Matters
  Ian Macaulayof Carp, Ontario
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/