ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: enableregime in mkiv
Date: Mon, 12 May 2008 10:55:00 +0200	[thread overview]
Message-ID: <6faad9f00805120155l30727b35nbe99246d12a7278f@mail.gmail.com> (raw)
In-Reply-To: <4827F9B8.4090101@elvenkind.com>

On Mon, May 12, 2008 at 10:03 AM, Taco Hoekwater wrote:
>
>
>  Hans van der Meer wrote:
>  > I am using MacOSX and up till now my files have a Western(Mac OS
>  > Roman) encoding, not UTF8. That works fime in ConTeXt-mkii by using
>  > \enableregime[mac].
>  > But in ConTeXt-mkiv through luatex I get an error despite that same
>  > \enableregime[mac]: For an accented character like é the error is "!
>  > Text line contains an invalid utf-8 sequence."
>
>  > How can I solve that
>  > other than changing all my files to UTF8 encoding?
>
>  Perhaps with a preprocessing (ctx) file that runs iconv, but luatex
>  itself wants UTF-8, full stop.

Well, even though - please do yourself a favor and do not use them -
regimes are still supported in mkiv (at least cp12xx and iso-8859-x),
but "mac" regime has not been added to the lua tables (just as many
other older regimes).

Two simple options that I always use for recoding files:
a) recode macintosh..UTF-8 your-file.tex
b) (if a fails for some reason)
vim your-file.tex
:e ++enc=macroman
:set fileencoding=utf-8
:wq

Recode needs to be installed from somewhere (with fink for example).

If you really really cannot leave without mac encoding, support can
still be added to mkiv. But in either case: do yourself a favor and
start using UTF-8.


On Mon, May 12, 2008 at 10:28 AM, luigi scarso wrote:
> >> Text line contains an invalid utf-8 sequence."
>  Ah yes, I rember: there are 2~3 tex files in base/
>  with this problem.
>  I have a list, but it's not update to last context distro (I will do soon) .
>  I believe that with file command (under linux) one can discover them.

supp-tpi.tex:           Non-ISO extended-ASCII English text
supp-mps.tex:           ISO-8859 English text
sort-lan.mkii:          Non-ISO extended-ASCII English text
regi-ibm.tex:           Non-ISO extended-ASCII English text, with LF,
NEL line terminators
ppchtex.tex:            Non-ISO extended-ASCII English text
m-pdfsnc.tex:           ISO-8859 English text
font-chi.tex:           ISO-8859 English text
enco-ini.tex:           Non-ISO extended-ASCII English text
enco-cyr.tex:           ISO-8859 English text
core-reg.tex:           ISO-8859 English text
core-lst.tex:           Non-ISO extended-ASCII English text
cont-new.tex:           ISO-8859 English text

>  Just for sure : no BOM problem ? I remember something about this in mkii
>  http://unicode.org/faq/utf_bom.html#BOM

BOM is usually removed automatically. The only problem that I have
discovered last time was when BOM was present in environment file in a
project. But:
- you can write files without BOM
- you can pass --utf option to texexec

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2008-05-12  8:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12  7:56 Hans van der Meer
2008-05-12  8:03 ` Taco Hoekwater
2008-05-12  8:16   ` Hans Hagen
2008-05-12 11:11     ` Hans van der Meer
2008-05-12 12:34       ` Hans Hagen
2008-05-12  8:28   ` luigi scarso
2008-05-12  8:55   ` Mojca Miklavec [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6faad9f00805120155l30727b35nbe99246d12a7278f@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).