From: "Procházka Lukáš" <lpr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Problem processing a non-UTF8 Lua script
Date: Thu, 21 Oct 2010 19:47:58 +0200 [thread overview]
Message-ID: <op.vkxs181q8lgizc@lk-2008-nbk> (raw)
In-Reply-To: <AANLkTimxVvm2CQF4o28FErykgwbSFDjnfOBxDd5AuOof@mail.gmail.com>
Well, I've done it by the proposed way in this particular case.
(I.e. I have the only one UTF-8 coded file - and this is the only one text file in general - for this one case.
TextPad supports various codings as well.
I was not sure whether the text editor will be able to determine coding used, so I worried about having to select encoding every time I'd like to edit this Lua file.
But, fortunately, the editor is able to determine the UTF-8 coding; and the CP1250 as well.
So once I saved this Lua file with UTF-8 encoding, I don't have to reselect it.)
Lukas
On Thu, 21 Oct 2010 17:49:43 +0200, Vedran Miletić <rivanvx@gmail.com> wrote:
> 2010/10/21 Procházka Lukáš <lpr@pontex.cz>:
>> Or how to make Ctx work with non-UTF8 Lua files?
>
> Notepad supports saving to UTF-8. Can't you rather convert your files to it?
>
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-10-21 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 8:00 Procházka Lukáš
2010-10-21 15:49 ` Vedran Miletić
2010-10-21 16:55 ` Mojca Miklavec
2010-10-21 17:04 ` Mojca Miklavec
2010-10-21 17:13 ` Hans Hagen
2010-10-21 18:32 ` Arthur Reutenauer
2010-10-21 17:47 ` Procházka Lukáš [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=op.vkxs181q8lgizc@lk-2008-nbk \
--to=lpr@pontex.cz \
--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).