[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #41965] __makeinfo__ assumes unsigned char for
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #41965] __makeinfo__ assumes unsigned char for input text when it should be signed char |
Date: |
Thu, 27 Mar 2014 02:14:48 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.152 Safari/537.36 |
Update of bug #41965 (project octave):
Status: None => Confirmed
Release: 3.6.2 => dev
_______________________________________________________
Follow-up Comment #1:
Confirmed already in the discussion on the mailing list. Also affects the
development version. Thanks for transcribing all of this detail to the bug
report.
Although, for this particular example, keep in mind that technically the
preferred texinfo formatting would be:
## -*- texinfo -*-
## @deftypefn {Function File} address@hidden =} fn (@var{x}, @dots{})
## The unicode character, @geq{}, is output
## @end deftypefn
And then it's up to the texinfo program to convert the macros to the output
format.
But yes, in general for other non-ASCII characters that would be useful to us,
like °, ×, µ, or even é this bug report still holds.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?41965>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/