[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49339] False error reports while producing la
From: |
Taneli Kalvas |
Subject: |
[Octave-bug-tracker] [bug #49339] False error reports while producing latex with non-ascii chars under gnuplot |
Date: |
Fri, 3 Mar 2017 06:25:31 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
Follow-up Comment #3, bug #49339 (project octave):
I am running octave processing script files on a server without interactive
prompt or display. The script files are supposed produce graphics. The same
conditions can be reproduced on any computer by running with
export DISPLAY=
export GNUTERM=png
octave --no-window-system --no-gui -qf test.m
with test.m being
plot([1 2 3],[3 4 2])
xlabel("\\alpha Äh")
print("image.png", "-dpngcairo")
one can see on the resulting image file that the LaTeX encoded alpha and the
utf-8 encoded umlaut character are properly rendered, but nevertheless Octave
prints out a warning from ft_text_renderer function referring to locale C even
if the locale is set to en_US.UTF-8 for example.
I do not agree on the original posters suggestion on changing the setlocale
(LC_CTYPE, 0) at libinterp/corefcn/ft-text-renderer.cc because that is
effectively a "getlocale" as it should. Still, somewhere during initialization
process octave should do setlocale (LC_CTYPE, ""). In
libinterp/corefcn/interpreter.cc as the op suggests? Another option is to use
main.cc where we have a if-else structure processing different conditions with
or without gui.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49339>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #49339] False error reports while producing latex with non-ascii chars under gnuplot,
Taneli Kalvas <=