[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnumed-devel] Encoding (viewing) on Mac OS
From: |
Busser, Jim |
Subject: |
[Gnumed-devel] Encoding (viewing) on Mac OS |
Date: |
Tue, 15 Nov 2011 04:50:15 +0000 |
Judging from my favourite Mac text processor TextWrangler -- a free version of
BBedit -- I think I figured out a Mac vulnerability when processing a file
encoded as
Latin1
because TextWrangler (perhaps with a dependency on the OS) has trouble to
appropriately auto-detect which form of Latin 1 encoding… it tends to select
Western (Mac OS Roman)
even when this results in incorrect characters e.g. in the server sql
country-specific file
gmDemographics-Data.ca.sql
it yields
<snip>
select i18n.upd_tx('fr_CA', 'Nova Scotia', 'Nouvelle-…cosse');
select i18n.upd_tx('fr_CA', 'Prince Edward Island',
'Œle-du-Prince-…douard');
select i18n.upd_tx('fr_CA', 'Quebec', 'QuÈbec');
<snip>
whereas
Western (Windows Latin 1)
Western (ISO Latin 1)
yield
<snip>
select i18n.upd_tx('fr_CA', 'Nova Scotia', 'Nouvelle-Écosse');
select i18n.upd_tx('fr_CA', 'Prince Edward Island',
'Île-du-Prince-Édouard');
select i18n.upd_tx('fr_CA', 'Quebec', 'Québec');
<snip>
If necessary, I can open such files manually choosing one of the other Latin1
encodings, change the selection to UTF8 and save it.
I wonder however whether in future -- in spite of the Canadian source having
been Latin 1 -- there is any reason why the sql files cannot be saved in UTF8?
-- Jim
- [Gnumed-devel] Encoding (viewing) on Mac OS,
Busser, Jim <=