Re: no worries (was: Editing Arabic TEI )
"Paterson, Duncan" <[email protected]>
| Newsgroups | gmane.text.tei.general |
|---|---|
| Message-ID | <15511B14-F403-47FF-B0C5-18B802BD837D@asia-europe.uni-heidelberg.de> |
Dear Ondine, My own work is I'm cjk, but I have helped a few colleagues and friends with other non-latin scripts to set up oxygen for tei work. The two basic problems I encounter most frequently are badly configured fonts. If the font configured in oxygen s preferences for displaying XML is not a good match (or simply the default) you will see strange artifacts or weird lines, despite everything being fine with the underlying tei files. The other problem relates to choosing utf8 or utf16 encoding, but I don't think double byte characters applies to Arabic. Greetings Duncan Sent from my phone > On 2 Feb 2017, at 23:36, Piotr Baski <[email protected]> wrote: > > Dear Ondine, > > That notice was most probably added by your Exchange / Outlook server upon receiving your own message redirected from TEI-L. It's Microsoft that doubts you, not the TEI crowd. _Our_ faith in you does not falter... :-) > > Best wishes, > > Piotr > > >> On 02/02/17 22:58, Ondine LeBlanc wrote: >> Okay, just need to add that I am not a fraud, really. This message is about XML and oXygen and Arabic characters. Really. Maybe the detector doesn't like the Turkish name? >> >> -----Original Message----- >> From: TEI (Text Encoding Initiative) public discussion list [mailto:[email protected]] On Behalf Of Ondine LeBlanc >> Sent: Thursday, February 02, 2017 4:50 PM >> To: [email protected] >> Subject: Re: Editing Arabic TEI >> >> [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] > > [...]