Am Sonntag, den 01.05.2011, 15:09 -0400 schrieb Aditya Mahajan:
> On Sun, 1 May 2011, Aditya Mahajan wrote:
>
> > On Sun, 1 May 2011, Peter Münster wrote:
> >
> >> So, whatever the original enviroment is, context and/or luatex sets
> >> LC_COLLATE=C
> >> LC_CTYPE=C
> >> LC_NUMERIC=C
> >
> > Confir
On Sun, 1 May 2011, Aditya Mahajan wrote:
On Sun, 1 May 2011, Peter Münster wrote:
So, whatever the original enviroment is, context and/or luatex sets
LC_COLLATE=C
LC_CTYPE=C
LC_NUMERIC=C
Confirmed. Now the question is, why does this cause pandoc to behave
strangely.
Perhaps due to a old
On Sun, 1 May 2011, Peter Münster wrote:
So, whatever the original enviroment is, context and/or luatex sets
LC_COLLATE=C
LC_CTYPE=C
LC_NUMERIC=C
Confirmed. Now the question is, why does this cause pandoc to behave
strangely.
Aditya___
Aditya Mahajan writes:
> *\directlua{os.execute("locale")}
Ok, locale outputs something depending on the enviroment. Lets look
directly at the enviroment:
$ CMD="set | grep -e ^LC_ -e ^LANG"
--8<---cut here---start->8---
$ eval $CMD
LC_CTYPE=en_GB.utf8
$ ec
Aditya Mahajan 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_PAPE
On Sun, 1 May 2011, Peter Münster wrote:
Aditya Mahajan writes:
(but I don't see why locale should be different when a
program is run from inside context then when it is run from a shell).
Taco can surely better explain why. I think somewhere in the luatex
manual, he explains why luatex set
Aditya Mahajan writes:
> (but I don't see why locale should be different when a
> program is run from inside context then when it is run from a shell).
Taco can surely better explain why. I think somewhere in the luatex
manual, he explains why luatex sets locale to "C".
To see the differences i
Am Samstag, den 30.04.2011, 11:10 -0400 schrieb Aditya Mahajan:
> On Sat, 30 Apr 2011, Paul Menzel wrote:
>
> > Am Freitag, den 29.04.2011, 18:13 -0400 schrieb Aditya Mahajan:
> >> On Fri, 29 Apr 2011, Paul Menzel wrote:
> >
> >>> the filter module installed using
> >>> does not work with the foll
On 2011-04-29 <23:09:42>, Paul Menzel wrote:
> Dear ConTeXt folks,
>
>
> the filter module installed using
>
> $ ./first-setup.sh --extras="t-filter"
>
> does not work with the following example, which is also attached.
>
> \usemodule[filter]
> \defineexternalfilter[rest]
On Sat, 30 Apr 2011, Paul Menzel wrote:
Am Freitag, den 29.04.2011, 18:13 -0400 schrieb Aditya Mahajan:
On Fri, 29 Apr 2011, Paul Menzel wrote:
the filter module installed using
does not work with the following example, which is also attached.
The output file `minimal-temp-rest.tex` is just
Am Freitag, den 29.04.2011, 18:13 -0400 schrieb Aditya Mahajan:
> On Fri, 29 Apr 2011, Paul Menzel wrote:
> > the filter module installed using
> >
> > $ ./first-setup.sh --extras="t-filter"
> >
> > does not work with the following example, which is also attached.
> >
> >\usemodule[fil
On Fri, 29 Apr 2011, Paul Menzel wrote:
Dear ConTeXt folks,
the filter module installed using
$ ./first-setup.sh --extras="t-filter"
does not work with the following example, which is also attached.
\usemodule[filter]
\defineexternalfilter[rest][filtercommand={pandoc -
Dear ConTeXt folks,
the filter module installed using
$ ./first-setup.sh --extras="t-filter"
does not work with the following example, which is also attached.
\usemodule[filter]
\defineexternalfilter[rest][filtercommand={pandoc -f rst -t context -o
\externalfilteroutpu
13 matches
Mail list logo
