From: pmlists@free.fr (Peter Münster)
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: t-filter: no table created when Unicode characters are included
Date: Sun, 01 May 2011 20:27:48 +0200 [thread overview]
Message-ID: <87ei4iz36j.fsf@micropit.couberia.bzh> (raw)
In-Reply-To: <alpine.LNX.2.01.1105011027370.5490@ybpnyubfg.ybpnyqbznva> (Aditya Mahajan's message of "Sun, 1 May 2011 10:29:21 -0400 (EDT)")
Aditya Mahajan <adityam@umich.edu> writes:
> $context --pipe
Oh, nice option, that I haven't known yet! :)
> *\directlua{os.execute("locale")}
> LANG=en_US.UTF-8
> LC_CTYPE="en_US.UTF-8"
Strange, here it's:
LANG=
LC_CTYPE=C
LC_NUMERIC=C
LC_TIME="POSIX"
LC_COLLATE=C
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
And in my environment:
LC_CTYPE=en_GB.utf8
When I add to my environment "LANG=en_GB.utf8", then the context output
is:
LANG=en_GB.utf8
LC_CTYPE=C
LC_NUMERIC=C
LC_TIME="en_GB.utf8"
LC_COLLATE=C
LC_MONETARY="en_GB.utf8"
LC_MESSAGES="en_GB.utf8"
LC_PAPER="en_GB.utf8"
LC_NAME="en_GB.utf8"
LC_ADDRESS="en_GB.utf8"
LC_TELEPHONE="en_GB.utf8"
LC_MEASUREMENT="en_GB.utf8"
LC_IDENTIFICATION="en_GB.utf8"
LC_ALL=
So luatex and/or context changes at least LC_CTYPE to C in my case. When
I set LC_ALL too, I get the same result as yours.
> so context no longer changes the locale.
Just a little bit in some cases ... ;)
--
Peter
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-05-01 18:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 21:09 Paul Menzel
2011-04-29 21:17 ` [t-filter] [PATCH] tests: add test file for reST (reStructuredText) Paul Menzel
2011-04-29 22:13 ` t-filter: no table created when Unicode characters are included Aditya Mahajan
2011-04-30 7:37 ` Paul Menzel
2011-04-30 15:10 ` Aditya Mahajan
2011-05-01 10:48 ` Paul Menzel
2011-05-01 12:12 ` Peter Münster
2011-05-01 14:29 ` Aditya Mahajan
2011-05-01 18:27 ` Peter Münster [this message]
2011-05-01 18:52 ` Peter Münster
2011-05-01 19:05 ` Aditya Mahajan
2011-05-01 19:09 ` Aditya Mahajan
2011-05-02 15:30 ` Paul Menzel
2011-05-27 8:53 ` [solved] " Paul Menzel
2011-06-23 14:31 ` yoraxe
2011-06-23 16:30 ` Aditya Mahajan
2011-06-23 19:59 ` t-filter: how to use math-mode yoraxe
2011-06-23 21:08 ` yoraxe
2011-06-23 23:23 ` Aditya Mahajan
2011-06-25 10:58 ` yoraxe
2011-04-30 21:00 ` t-filter: no table created when Unicode characters are included Philipp Gesang
2011-05-20 9:24 ` t-rst: Unicode character not printed (was: t-filter: no table created when Unicode characters are included) Paul Menzel
2011-05-20 9:54 ` Philipp Gesang
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=87ei4iz36j.fsf@micropit.couberia.bzh \
--to=pmlists@free.fr \
--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).