Simon Thanks for this explanation of these very welcome FH5 features. I have just one question for clarification. I export my gedcom to my UTF-8 TNG website and would like to know if I will need do a 'Save-as' in UTF-8 or is there a 'Preferences' setting to always save as UTF-8 or whatever else the user may prefer? Graham http://www.katiandgraham.com/genealogy On 05/12/2011 11:03, Simon Orde wrote: > Apologies in advance to non-technical readers. This is a technical > question, so the answer will inevitably also be technical. Read on if still > interested... > > Graham - > > internally FH will continue to use ANSI, but it will do a proper import > from, and export into, UTF-8 (and also from/to Unicode, ANSEL and ASCII) - > i.e. accent characters in UTF-8 or Unicode etc will be correctly converted > to ANSI , or vice versa; which they weren't previously in V4. When > generating websites, the generated webpages will be correctly encoded as > UTF-8 (which is pretty much the standard for web-pages these days). Also, > if you simply open a GEDCOM file that was saved in UTF-8, Unicode etc, FH > will correctly convert it into ANSI. > > What this means is that if you use accent characters which are supported in > ANSI, in an ordinary English-language installation of Windows (and that > includes a lot of accent characters, including all those required for a > number of European languages such as French and German) you should find that > these accent characters should now be fine in all contexts in V5 - i.e. they > import correct, display correctly in the program (assuming you don't choose > some strange font or font encoding), export correctly, and display correctly > in generated websites. > > Windows provides a mechanism to help people who use certain languages with > accent characters which are not supported in a default English-language > installation of Windows - e.g. I think Czech falls into this category. > There is a "Regional and Language options" setting in the control panel > which allows you to specify one preferred language for non-Unicode programs > to use. If you use this system for your preferred language, this also > should work in V5. > > For interest, our impression, based on GEDCOM files that we have encountered > (which is a lot), is that far more than 90% of them are encoded in ANSI. > > Hope that makes sense. > > Simon Orde > List Administrator& Family Historian designer > > ----- Original Message ----- > From: "Graham Chamberlain"<agc@katiandgraham.com> > To: "Family-Historian Users"<Family-Historian-USERS@rootsweb.com> > Sent: Friday, December 02, 2011 7:03 PM > Subject: [FHU] UTF8 Supported in v5? > > >> Can anyone tell me if UTF8 character set will be supported in the >> forthcoming FH v5 or will it still >> only be ANSI? >> >> Graham >> http://www.katiandgraham.com/genealogy >> >> >> ------------------------------- >> To unsubscribe from the list, please send an email to >> FAMILY-HISTORIAN-USERS-request@rootsweb.com with the word 'unsubscribe' >> without the quotes in the subject and the body of the message > > ------------------------------- > To unsubscribe from the list, please send an email to FAMILY-HISTORIAN-USERS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message >