quotes

[Connie Marks]

I note that when I upload my gedcom created by T2G that I am getting strange results for some of my Quoted names

in TMG: Lenore Marie “Tiny”    

In the gedcom: 1 NAME Lenore Marie “Tiny” /Lawrence/

in ancestry:

Lenore Marie ́��Tiný�� Lawrence

1926–20  Add MyTreeTags™

 

--

Connie Marks

Cell 817-480-7469

[John Cardinal]

Connie,

 

If you copied the text to the email message without modifying it, those are not "straight" quotes, they are "curly" quotes.

 

1. Perhaps Ancestry doesn't like curly quotes?

 

2. You didn't change the character encoding of the GEDCOM file before uploading, did you?

(T2G always writes UTF-8 files, but if you edit it the GEDCOM file before uploading to Ancestry, you might have changed the encoding.)

 

John Cardinal

 

Products: ORA, GedSite, Gedcom Publisher, Second Site, TMG Utility, TMG to GEDCOM

Web Hosting for Genealogists: Family History Hosting

[Connie Marks]

I copied the text into to the email, and no I did not change the character encoding.  Later I will do some additional testing, I don't recall how the data in TMG was created with the curly quotes, I suspect it was a copy from some other place, as I avoid typing if I can copy paste.  The reason I ask was that I have only seen this on the last few uploads to ancestry.  I can not say they are doing something different, my guess it is the TMG source.  

Does TMGU have the ability to convert to UTF-8? (or T2G?)

--
You received this message because you are subscribed to the Google Groups "TMG to GEDCOM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to t2g-l+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/t2g-l/001001da82b7%2461c97670%24255c6350%24%40gmail.com.

[John Cardinal]

Connie,

 

Regarding the email message text, email clients sometimes convert characters as part of "correcting" what you key or copy/paste. So, for example, you key a straight quote after keying a space and the email client converts it to a left-hand curly quote. My question was whether that was a factor in the email you sent.

 

TMG does not support Unicode. My programs read the text using the appropriate "code page" (Windows character encoding), and then T2G writes to the GEDCOM file using the UTF-8 character encoding.

 

If the prior versions of your TMG data had curly quotes, then my guess would be opposite yours: I'd suspect Ancestry is doing something differently.

 

You can't convert TMG's text data to UTF-8 because TMG wouldn't know what to do with it. If you want to use straight quotes, you can use TMGU's Find and Replace feature to change “ and ” to ".

To view this discussion on the web visit https://groups.google.com/d/msgid/t2g-l/CAPWJxLjZ9wyzpRdLJMjdwoN%3DNBHW_Fzu%2Bsgnkmwmq4kW2k9j7Q%40mail.gmail.com.

[Connie Marks]

I found the issue. I used ORA to copy the Given Name via a straight copy from the control panel to the given name field in TMG. I did NOT use a template.  But I just created an autotype template and it created the same results, the quotes are curley

https://www.findagrave.com/memorial/67358370

and yes, ancestry does not like curley quotes. 

To view this discussion on the web visit https://groups.google.com/d/msgid/t2g-l/002b01da82ce%24bdb9df80%24392d9e80%24%40gmail.com.