OT-ish warning: Apple is still using Mac Roman

[Richmond]

On 31/01/14 07:10, Kay C Lan wrote:
> Via the Apple Support forums.
>
> Pages is unicode. It can import, export and work with unicode no problem.
>
> An issue it does have, and seems to be right in line with your problem,
> someone was working with a Pages documents that was full of mathematical
> formuli and these all came out mac roman; which was then a problem when it
> was sent outside the Mac garden. The suggested reason was that maybe
> someone had imported these (copied and pasted) from another Mac program and
> this was not a unicode program but was handled by Pages because it's
> bilingual.

This makes very good sense indeed.

I have a large number of documents I wrote in Clarisworks/Appleworks in 
1992-6 on Macs
running Mac OS 7 - 8.6 in Bulgarian using svseral of those Mac ttf fonts 
ending in CYR or BG.

Obviously they do not adhere to the Unicode standard.

They can be opened in a readable format by Pages.

Yesterday I hooked up my SCSI ZIP drive via a fairly outrageous 
spaghetti of cables to a USB port
and imported a document written in 1995 into Pages; no probs there. When 
I exported it to .doc format and opened
it with Libre Office on Linux I got something that was totally unreadable.

I typed some Bulgarian directly into Pages and exported that as a .doc 
thing, and opened it with Libre Office with no probs
at all.

Kay C Lan has, successfully, stated what I spent most of the night 
trying to understand.

Richmond.

>
> So if YOU create the Pages document, and you make sure everything you put
> into it is unicode, then other unicode compatible programs will see the
> characters correctly.
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode