ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: UTF conversion via Lua
Date: Fri, 10 Feb 2012 12:15:29 +0100	[thread overview]
Message-ID: <A3E152D5-6C86-4F65-ACC0-CF6BA08C50A3@googlemail.com> (raw)
In-Reply-To: <op.v9gmovrzwshuv7@lpr>


Am 10.02.2012 um 12:11 schrieb Procházka Lukáš Ing. - Pontex s. r. o.:

> ... Well, my information was not correct.
> 
> There are characters > 127 in the file, like "ř", "š"...
> 
> Each char = 1 byte, and as I'm using Windows with CP 1250, the characters are displayed correctly.
> 
> But I have problem loading them into ConTeXt.
> 
> I need to convert the bytes > 127 to UTF sequence, which would be acceptable by ConTeXt.
> 
> @Thomas:
> 
> The table looks nice but there are no entries for CP 1250 to UTF conversion.
> 
> I prepared some tables: character conversion and removal of diacritics (see the attachment);
> maybe it would be handful to include them into ConTeXt somehow.

Why don’t you let do context the conversion:

\starttext

this is something in utf8

\startregime[cp1250]
\input filewithcp1250encoding
\stopregime

more text encoded in utf8

\stoptext

Wolfgang
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2012-02-10 11:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 10:22 Procházka Lukáš Ing. - Pontex s. r. o.
2012-02-10 10:26 ` Thomas A. Schmitz
2012-02-10 10:57 ` Philipp Gesang
2012-02-10 11:11   ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-02-10 11:14     ` luigi scarso
2012-02-13 11:42       ` Ulrike Fischer
2012-02-13 13:14         ` luigi scarso
2012-02-10 11:15     ` Wolfgang Schuster [this message]
2012-02-10 11:32       ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-02-10 12:25         ` Wolfgang Schuster
2012-02-10 13:15           ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-02-10 15:08             ` Hans Hagen
2012-02-16 11:13           ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-02-16 12:08             ` Hans Hagen
2012-02-16 13:15               ` UTF conversion via Lua (renaming attachments to .scr_) Procházka Lukáš Ing. - Pontex s. r. o.
     [not found]               ` <op.v9rwejuttpjj8f@lpr>
2012-02-16 22:56                 ` Hans Hagen
2012-02-17  8:09                   ` UTF conversion via Lua Procházka Lukáš Ing. - Pontex s. r. o.
2012-02-17  8:19                     ` Hans Hagen
2012-02-17  9:20                       ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-02-10 11:40       ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-02-10 11:30     ` Philipp Gesang
2012-02-10 11:13   ` UTF conversion via Lua (now with attachment) Procházka Lukáš Ing. - Pontex s. r. o.

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=A3E152D5-6C86-4F65-ACC0-CF6BA08C50A3@googlemail.com \
    --to=schuster.wolfgang@googlemail.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).