ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: UTF conversion via Lua
Date: Thu, 16 Feb 2012 13:08:09 +0100	[thread overview]
Message-ID: <4F3CF1A9.6030904@wxs.nl> (raw)
In-Reply-To: <op.v9rqsdu3wshuv7@lpr>

On 16-2-2012 12:13, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
> Hello,
>
> one more question -
>
> - does "regimes.translate" allow to translate between arbitrary
> encodings or only from the specified to the current one?

no, although it's no big deal to provide that (of course there is then 
the matter of utf being more complete than the target)

> ----
> str = regimes.translate(str, "cp1250") -- = Translate from "cp1250" to
> the current encoding (UTF) (or always to UTF?)
> ----
>
> I'm looking for something like:
>
> ----
> src_enc = "utf8"
> tgt_enc = "cp1250"
>
> str = regimes.translate(str, src_enc, tgt_enc)
> ----
>
> Any idea?

is there a reason not to stick to utf?

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2012-02-16 12:08 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
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 [this message]
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=4F3CF1A9.6030904@wxs.nl \
    --to=pragma@wxs.nl \
    --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).