- This topic has 2 replies, 2 voices, and was last updated 6 months ago by .
Many issues related to diacritics (e.g. ë, è, é…) have been reported in the past. ABCD as an ISIS-family member deals with ‘international’ (also non-anglosaxon) content relatively more often and conversion from one encoding set (or codepage) to another is necessary quite regularly, e.g. moving from CDS/ISIS for DOS (CP437) to WinISIS (CP850 or ANSI) and to more current encoding like ISO-8859-1 or UTF8 as used in browsers.
CISIS provides ‘gizmo’ tables (actually : ISIS databases with fields v1 and v2, resp. defining ‘from’ and ‘to’ values) to convert from one to another. So in principle all tools are available to deal with diacritics.
Still we ran into a weird issue :
- – a MST file opened with just a text-viewer and using its ‘CP437’ codepage shows the diacritics correctly
- – however in ABCD the diacritics are wrong
- – applying the gizmo ‘g437ansi’ (from CP437 to ANSI) while in principle being the solution doesn’t solve the problem : the diacritics remain wrong.
– further testing/experimenting shows that ANY action with mx will change the diacritics in the MST, disallowing the correct diacritics even in CP437 ! E.g just creating a copy of the database with the mx-utility (both in Windows and Linux) means that the MST of the resulting copy no longer can be viewed correctly, even with CP437. Printing the records to an ISO2709-file : same. Dumping to a text-file : same.
Even an old pre-ABCD version of mx was used to test this but the result remains : any processing with mx will lose the diacritics (no codepage shows them correctly anymore).
Does anybody see what is happening here ? How to preserve the correct diacritics – which are there as can be seen when viewing the MST with CP437 but show up wrongly in any other process or environment (ABCD, ISO2709, …) ?
Illustration : viewing same sample text with diacritics with CP437 before (original) and after (copy of original, created with mx) :
- You must be logged in to reply to this topic.