Also, is wrong for dark gray. It assumes dim is mapped to dark
gray, but tput reset and tput oc do not enforce this, and .e.g Ubuntu
defaults to a different mapping (cyan?) for this attribute. Worse, in some
console drivers (fbcon?) the "dim" and "underline" attribute color mappings
are conflated.
A further correction: it should be ncv#63 to exclude standout too, since
standout is implemented using reverse-video. Also, is buggy. It
tries to use dim in conjunction with black to achieve dark grey as a
background, but this actually only works for a dark gray foreground. A
correct would be:
My mistake, it should be ncv#62 to exclude , since that's how bright
background colors are achieved.
On Sat, Mar 16, 2013 at 3:28 PM, Ben Wiley Sittler wrote:
> Sorry, my mistake!
>
>
> On Sat, Mar 16, 2013 at 1:19 PM, Thomas Dickey wrote:
>
>> I'm confused by your comment, since the linux-16co
Sorry, my mistake!
On Sat, Mar 16, 2013 at 1:19 PM, Thomas Dickey wrote:
> I'm confused by your comment, since the linux-16color entry does use
> ncv#54
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/438413
>
> Title
It turns out there's still a bug in this entry: needs to be adjusted
to ncv#54
On Thu, Dec 15, 2011 at 5:50 PM, Thomas Dickey wrote:
> ** Changed in: ncurses (Ubuntu)
>Status: New => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report
FYI, the patch has not been sent upstream or reviewed by anyone yet, but
please feel do send it upstream if it seems useful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998612
Title:
zhcon KSC and
** Patch added: "Improve zhcon KSC and JIS support"
https://bugs.launchpad.net/bugs/998612/+attachment/3143605/+files/zhcon-ksc-and-jis-fixes.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9986
Public bug reported:
Attempting to set the default encoding to KSC in .zhconrc or
/etc/zhcon.conf fails and actually sets the encoding to GBK. Here's the
relevant config file line:
defaultencode = ksc
Also any attempt to use --utf8 with KSC or JIS fails since iconv does
not know those charset na
Sorry, Ubuntu box has been down for >1yr here :(
On Wed, Mar 17, 2010 at 19:51, Arne Goetje wrote:
> ** Changed in: ttf-uralic (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: ttf-uralic (Ubuntu)
> Status: Incomplete => Triaged
>
> --
> MonoUralic contains incorrect encoding inf
** Attachment added: "Patch to use glibc's iconv extension //TRANSLIT to
automatically handle untranslatable output"
http://launchpadlibrarian.net/32761294/zhcon-utf8.diff
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32761295/Dependencies.txt
--
zhcon --utf8 trun
Public bug reported:
Binary package hint: zhcon
When run with the --utf8 option, zhcon internally converts client output
from UTF-8 to the internal zhcon encoding (GB2312/GBK/EUC-KR/etc.) and
does the corresponding reverse translation to UTF-8 for input from the
user. However, when a character in
The and in the "linux-16color" entry in my patch are
broken for color 8. To fix them, replace both instanced of %{8}%> with
%{7}%> and all colors should then work.
--
init_color (and the capability) for terminal type "linux" fails when
red, green and/or blue is set to the maximum value (1000)
Public bug reported:
When using init_color(3ncurses) or the underlying capability,
the red, green and blue color components are specified on a scale of 0
to 1000, inclusive. However, the terminfo data for the "linux" terminal
type has a buggy which fails for component value 1000 (full
intensity.
** Attachment added: "Fixes for "linux" and friends, and similar bugs
in a couple other terminfos; also added a "linux-16color" entry for fbcon with
256-position font"
http://launchpadlibrarian.net/32635354/linux-terminfo.diff
--
init_color (and the capability) for terminal type "linux" f
** Attachment added: "Patch to fix SGR handling for up to 10 parameters"
http://launchpadlibrarian.net/32494337/bogl-bterm.diff
--
SGR handling is broken
https://bugs.launchpad.net/bugs/437314
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
bogl-bterm's handling of Set Graphic Rendition sequences is broken in two ways:
1. SGR0 does not reset underlining
2. in a multi-parameter SGR, only the first parameter has any effect
ProblemType: Bug
Architecture: i386
Dependencies:
libgcc1 1:4.3.3-5ubuntu4
gcc-4.3-base 4.
That sounds good to me. As I said, once I have access to an Ubuntu
machine again, I will test.
On Sun, Jan 18, 2009 at 8:04 PM, Arne Goetje wrote:
> I will fix the _package_ in that regard, that the font does not get used
> automatically and that the replacement configurations are removed.
> Mean
Hi, Arne.
Both of my Ubuntu boxes are currently down and have been for some
months. I will test as soon as I have one of them working again.
Sorry for the delay!
-Ben
On Mon, Nov 10, 2008 at 8:05 PM, Arne Goetje <[EMAIL PROTECTED]> wrote:
> need feedback. does the proposed solution work for you
Hi, Arne.
Both of my Ubuntu boxes crashed (different reasons in each case) a
couple months ago. I don't know when I'll be able to get them working
again, but I will test this when I do.
I do apologize for the inconvenience!
-Ben
--
MonoUralic contains incorrect encoding information
https://bug
Public bug reported:
Binary package hint: bcc
I ran into a problem while trying to compile this file:
/*
home.c - home the cursor using Borland-style conio
compile with:
bcc -ansi -Md -o home home.c
*/
#include
int main(int argc, char **argv)
{
gotoxy(1,1);
return 0;
}
The error was:
u
my mistake, i misread your update. the new font works correctly for the
modified cp1251 encoding, but fails horribly (as before) in unicode-
aware applications.
--
MonoUralic contains incorrect encoding information
https://bugs.launchpad.net/bugs/73211
You received this bug notification because y
i installed and tested this font (with no other uralic fonts present),
and it still does not work correctly. it does not seem to contain
correct unicode mappings, or at least it does not display the special
udmurt and mari characters in firefox (firefox falls back on a
different font, freemono perh
Yes, the bug is only with the Unicode mapping. The 8-bit encoding
seems well-established and correct.
And I can confirm that this package still has this bug on my system :(
On 9/6/07, Arne Goetje <[EMAIL PROTECTED]> wrote:
> >From the README file:
> ---
i can confirm this in feisty:
$ rhino
Exception in thread "main" java.lang.NoClassDefFoundError:
org.mozilla.javascript.tools.shell.Main
at gnu.java.lang.MainThread.run(libgcj.so.70)
Caused by: java.lang.ClassNotFoundException:
org.mozilla.javascript.tools.shell.Main not found in
gnu.gcj.run
just fyi, the version: 0.0.20040829-1ubuntu1
--
MonoUralic contains incorrect encoding information
https://launchpad.net/bugs/73211
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: ttf-uralic
the MonoUralic font (/usr/share/fonts/truetype/uralic/monou___.ttf)
has incorrect character map information and so displays characters in
the Unicode range U+0080 ... U+00FF incorrectly (as cyrillic.) this is
especially a problem since the pack
btw, i can confirm that this fix has been applied in edgy on the
following python interpreters:
python2.4 2.4.3-8ubuntu2
python2.5 2.5-0ubuntu1
however it's still broken in the following edgy python:
python2.3 2.3.5-15ubuntu1
and in dapper it's broken too, at least in the version i have install
this bug does not appear to be actually fixed in version
2.4.3-8ubuntu1 (i.e. the patch has not been applied):
$ apt-cache show python2.4 | fgrep Version
Version: 2.4.3-8ubuntu1
Version 2.4 of the high-level, interactive object oriented language,
Python-Version: 2.4
$ python2.4 -c 'assert(repr(u"
Thanks! Perhaps this will inspire me to write a patch for the buggy
UTF-7 codec...
On 8/22/06, Simon Law <[EMAIL PROTECTED]> wrote:
> It appears that Georg Brandl has applied this patch.
>
> It should show up in the next release of Python 2.4.
>
> ** Bug watch added: Python at Sourceforge #1541585
thanks! let me know if they need any more info from the systems i tested
this on.
--
buffer overrun in repr() for unicode strings
https://launchpad.net/bugs/56633
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
i don't care who gets credit and i'm really busy. can you send it
upstream?
btw, i've attached the patch.
--
buffer overrun in repr() for unicode strings
https://launchpad.net/bugs/56633
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
Public bug reported:
hi,
i discovered a bug yesterday in repr() for unicode strings. this
causes an unpatched non-debug wide (UTF-32/UCS-4) build of python to
abort:
python2.4 -c 'assert(repr(u"\U0001" * 39 + u"\u" * 4096)) ==
(repr(u"\U0001" * 39 + u"\u" * 4096))'
the problem i
32 matches
Mail list logo
