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>
Cc: Wolfgang Werners-Lucchini <wwl@musensturm.de>
Subject: Re: mkiv and unicode
Date: Tue, 16 Mar 2010 17:40:48 +0100	[thread overview]
Message-ID: <4B9FB490.7000800@wxs.nl> (raw)
In-Reply-To: <4B9FBC91.15944.1B2608F@wwl.musensturm.de>

On 16-3-2010 17:14, Wolfgang Werners-Lucchini wrote:
> Hallo,
>
>>> I work all the time with good old mkii-context, but I have had a lot
>>> of problems last time, which could be solved easely if I switch to
>>> mkiv. So I wonder if I should change. The main argument for me to
>>> stay with mkii is the following:
>>>
>>> I have a lot of lua scripts withhin scite which are preprocessing my
>>> textfiles (string.gsub etc.) These scripts depent on ansi-code and do
>>> not work with unicode too.
>>>
>>> An other problem I have, is to teach scite to use utf-8 per default.
>>> (code.page=65001) does not work for me. I have tried this with a
>>> lot of versions of scite.
>>
>> code.page=65001
>> output.code.page=65001
>
> I have tried this very often. I have tried this in a fresh scite
> installation uncommenting this in the global propertie file. But it
> doesn't work.
> File->Encoding is Code Page Property. And my files are saved in Ansi.

strange

> I do not want look every time if I have saved with the proper
> encoding. I do not want files with ansi and files in utf mixed. I
> have considered to change the editor, but I very like the lua
> ability.
>
>>> Has anybody experiences with scite-lua-scripts and unicode?
>>
>> it depends on what you do but normally lua does not care about funny
>> characters in strings
>>
>> an option is to run the script outside scite and pipe data back
>
> Yes, this should allow one to use special librarys. I have heard of
> 'slnunicode' but haven't tested it yet.

you can then just use texlua which has this built in

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 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:[~2010-03-16 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.947.1268675147.26807.ntg-context@ntg.nl>
2010-03-16 16:14 ` Wolfgang Werners-Lucchini
2010-03-16 16:40   ` Hans Hagen [this message]
2010-03-15 17:27 Wolfgang Werners-Lucchini
2010-03-15 17:45 ` Hans Hagen

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=4B9FB490.7000800@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=wwl@musensturm.de \
    /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).