Western European Encoding vs Unicode

Question

Hi all,

I am working on migrating a user to Paratext 8 and noticed that their translation project is still in Western European encoding (1252) instead of Unicode. They do NOT have any special characters.

Is there a reason that they SHOULD convert to Unicode? If they DON’T convert to Unicode, are there foreseeable problems in the future with publishing (to print, web, or Scripture app)?

Thank you,

SIL+LSS+PNG

Answer 1

Not converting to Unicode may limit future options. For example, suppose I want to use a thin space or some other character not in code page 1252. I either have to go through the conversion process or give up on my choice. Why not do it now rather than waiting?

anon806807

Comments

It should do no harm to convert and could well avoid problems later on. Are the open/close quote characters in the Unicode set ANSI? Thin space is often inserted between nested quote markers at typesetting time, and non-breaking hyphen/space are useful also.

KimB