2010/2/11 Patric Mueller bh...@gmx.net:
Michal Suchanek hramr...@centrum.cz wrote:
2010/2/7 Patric Mueller bh...@gmx.net:
Michal Suchanek hramr...@centrum.cz wrote:
On 6 February 2010 15:23, Patric Mueller bh...@gmx.net wrote:
I'm not sure that the not so common cases you're thinking of are
Michal Suchanek hramr...@centrum.cz wrote:
2010/2/7 Patric Mueller bh...@gmx.net:
Michal Suchanek hramr...@centrum.cz wrote:
On 6 February 2010 15:23, Patric Mueller bh...@gmx.net wrote:
I'm not sure that the not so common cases you're thinking of are that
rare. For example, my OS is
Michal Suchanek hramr...@centrum.cz wrote:
On 6 February 2010 15:23, Patric Mueller bh...@gmx.net wrote:
Michal Suchanek hramr...@centrum.cz wrote:
FWIW here is a patch that
a) tries to detect if user is running in utf-8 locale by a heuristic
similar that that used in the autoconf test
2010/2/7 Patric Mueller bh...@gmx.net:
Michal Suchanek hramr...@centrum.cz wrote:
On 6 February 2010 15:23, Patric Mueller bh...@gmx.net wrote:
Michal Suchanek hramr...@centrum.cz wrote:
FWIW here is a patch that
a) tries to detect if user is running in utf-8 locale by a heuristic
similar
Michal Suchanek hramr...@centrum.cz wrote:
FWIW here is a patch that
a) tries to detect if user is running in utf-8 locale by a heuristic
similar that that used in the autoconf test
setlocale(LC_CTYPE, ) only sets the current LC_CTYPE to the value of
the user environment.
If e.g. the user
On 6 February 2010 15:23, Patric Mueller bh...@gmx.net wrote:
Michal Suchanek hramr...@centrum.cz wrote:
FWIW here is a patch that
a) tries to detect if user is running in utf-8 locale by a heuristic
similar that that used in the autoconf test
setlocale(LC_CTYPE, ) only sets the current
FWIW here is a patch that
a) tries to detect if user is running in utf-8 locale by a heuristic
similar that that used in the autoconf test
b) allows setting the unicode locale at runtime (changes the define to
a variable)
The autoconf script is not modified, removing the define should be
trivial
Christian Ohm chr@gmx.net wrote:
On Saturday, 30 January 2010 at 18:37, Siegfried-Angel Gevatter Pujals wrote:
I am sorry I didn't reply to this before. I had some difficulties with
it and it ended slipping out of radar.
Basically what I did to get Vilistextum to compile with multibyte
2010/2/4 Patric Mueller bh...@gmx.net:
I downloaded and run the debian-testing-i386-netinst.iso and then
[...]
Both versions just worked.
I guess that ISO comes with the locales for English then.
(By the way, if you want a build environment more like that of the
buildds, you can use eg.
On 4 February 2010 18:34, Siegfried Gevatter rai...@ubuntu.com wrote:
2010/2/4 Patric Mueller bh...@gmx.net:
I downloaded and run the debian-testing-i386-netinst.iso and then
[...]
Both versions just worked.
I guess that ISO comes with the locales for English then.
(By the way, if you want
Hi,
I am sorry I didn't reply to this before. I had some difficulties with
it and it ended slipping out of radar.
Basically what I did to get Vilistextum to compile with multibyte is
adding a build-dependency on locales-all and adding the following
line to debian/rules:
On Saturday, 30 January 2010 at 18:37, Siegfried-Angel Gevatter Pujals wrote:
I am sorry I didn't reply to this before. I had some difficulties with
it and it ended slipping out of radar.
Basically what I did to get Vilistextum to compile with multibyte is
adding a build-dependency on
2010/1/30 Christian Ohm chr@gmx.net:
I've compiled it with only --enable-multibyte, and that compiles and runs.
Needs -u to output UTF8 though, maybe that should be default.
Yeah, it does when you compile it locally, but not when you do so in a
chroot :/.
--
Siegfried-Angel Gevatter
13 matches
Mail list logo
