ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: Problem with encoding, XML and writetolist...
Date: Mon, 3 Apr 2006 14:33:06 +0200	[thread overview]
Message-ID: <6faad9f00604030533kbee9b61n6f0f97e962c41883@mail.gmail.com> (raw)
In-Reply-To: <FDEFJKLKHEOCDJPCFCIJAENPDJAA.martin.kolarik@email.cz>

On 4/3/06, Martin Kolařík wrote:

> which is not good. And I am not able, when not using cp1250.tcx, recode win1250 (default for win) to latin2. There I am able to write regime for myself (cp1250), but I suppose, that whenever characters will not expand to \char XXX form, cp1250.tcx still will be working and usable.

Hans, I would guess that more than 50% of Slavic Windows users (ie.
Slovenian, Croatian, Chech, Slovak, ...) use the cp1250 encoding
(including me). Would it be possible to add at least this file
http://pub.mojca.org/tex/enco/contextbase/regi-cp1250.tex to the
default ConTeXt distribution? (with "synonyms" windows-1250 and
cp1250).

This has probably nothing to do with the problem described here, but I
believe that many users would appreciate to have that "encoding"
(called regime in ConTeXt) available.

> when I added \mainlanguage[cz] before \enableregime[windows] in 8bit.tex and run
> texexec with --translate=cp1250cs, I got:

\enableregime[windows] is cp1252 (Western European Windows) not cp1250
(Central European Windows), --translate=cp1250cs is cp1250 (supposing
that you don't use \enableregime[windows], but the default one):
everything will be mixed up if you use both simultaneously.

If you download the file mentioned above (place it into the current
directory or somewhere in the TeX tree and refresh the filename
database) or if Hans adds it to the distribution, you can use
\input regi-cp1250
\enableregime[cp1250]

This probably won't solve your problem with missing spaces (didn't try
it), but you'll have the proper encoding.

Mojca

  reply	other threads:[~2006-04-03 12:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28  7:24 Martin Kolařík
2006-02-28  9:15 ` Hans Hagen
2006-02-28  9:33   ` Martin Kolařík
2006-03-31  8:42     ` Martin Kolařík
2006-03-31 17:01       ` Hans Hagen
2006-04-02 21:17         ` Martin Kolařík
2006-04-03  8:36           ` Hans Hagen
2006-04-03  8:57             ` Martin Kolařík
2006-04-03  9:56               ` Hans Hagen
2006-04-03 10:36                 ` Martin Kolařík
2006-04-03 12:33                   ` Mojca Miklavec [this message]
2006-04-03 12:39                     ` Martin Kolařík
2006-04-03 11:18                 ` Vit Zyka
2006-04-03 11:45                   ` Martin Kolařík
2006-04-04 20:18                 ` Martin Kolařík
2006-04-04 20:25                 ` Martin Kolařík
2006-04-05  8:17                   ` Hans Hagen
2006-04-05  9:54                   ` Vit Zyka
2006-04-05 11:03                     ` Hans Hagen
2006-04-05 12:18                       ` Vit Zyka
2006-04-05 14:09                         ` Hans Hagen
2006-04-03 14:25 ` Mojca Miklavec
2006-04-03 14:41   ` Martin Kolařík
  -- strict thread matches above, loose matches on Subject: below --
2006-04-05 11:59 Martin Kolařík
2006-04-06  9:07 ` Hans Hagen
2006-04-02 21:20 Martin Kolařík
2006-02-27 11:58 Martin Kolařík

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=6faad9f00604030533kbee9b61n6f0f97e962c41883@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).