Re: [Bug 438413] Re: init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000)
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. In others (e.g. vga) they are separated as documented in
console_codes(4).
The fix is to just use bright black for gray, which works reliably:
setaf=\E[3%p1%{8}%m%d%?%p1%{7}%>%t;1%e;21%;m,
On Wed, Mar 20, 2013 at 5:20 PM, Ben Wiley Sittler
wrote:
> 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:
>
> setab=\E[4%p1%{8}%m%d%?%p1%{7}%>%t;5%e;25%;m,
>
>
> The previous also failed to clear a previous blink when setting a
> dark gray background, causing inconsistent behavior.
>
> On Sat, Mar 16, 2013 at 3:33 PM, Ben Wiley Sittler wrote:
>
>> 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-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:
init_color (and the capability) for terminal type "linux"
fails when red, green and/or blue is set to the maximum value (1000)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/438413/+subscriptions
>>>
>>>
>>
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/438413
Title:
init_color (and the capability) for terminal type "linux"
fails when red, green and/or blue is set to the maximum value (1000)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/438413/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 438413] Re: init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000)
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:
setab=\E[4%p1%{8}%m%d%?%p1%{7}%>%t;5%e;25%;m,
The previous also failed to clear a previous blink when setting a
dark gray background, causing inconsistent behavior.
On Sat, Mar 16, 2013 at 3:33 PM, Ben Wiley Sittler
wrote:
> 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-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:
>>> init_color (and the capability) for terminal type "linux"
>>> fails when red, green and/or blue is set to the maximum value (1000)
>>>
>>> To manage notifications about this bug go to:
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/438413/+subscriptions
>>>
>>
>>
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/438413
Title:
init_color (and the capability) for terminal type "linux"
fails when red, green and/or blue is set to the maximum value (1000)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/438413/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 438413] Re: init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000)
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-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: >> init_color (and the capability) for terminal type "linux" >> fails when red, green and/or blue is set to the maximum value (1000) >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/438413/+subscriptions >> > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/438413 Title: init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/438413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 438413] Re: init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000)
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: > init_color (and the capability) for terminal type "linux" > fails when red, green and/or blue is set to the maximum value (1000) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/438413/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/438413 Title: init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/438413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 438413] Re: init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000)
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. > https://bugs.launchpad.net/bugs/438413 > > Title: > init_color (and the capability) for terminal type "linux" > fails when red, green and/or blue is set to the maximum value (1000) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/438413/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/438413 Title: init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/438413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998612] Re: zhcon KSC and JIS support somewhat broken
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 JIS support somewhat broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zhcon/+bug/998612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998612] Re: zhcon KSC and JIS support somewhat broken
** 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/998612 Title: zhcon KSC and JIS support somewhat broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zhcon/+bug/998612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998612] [NEW] zhcon KSC and JIS support somewhat broken
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 names; rather, it calls JIS "EUC-JP" and KSC "EUC-KR". This behavior was seen in Ubuntu 12.04 LTS with zhcon version 1:0.2.6-8 on architecture amd64, but I believe the problem has been present for years on all architectures. Hopefully fixing this will make Ubuntu more viable in the subset of Japanese and Korean applications where an fbcon-analogue with double- byte semantics is desirable. Please find a patch attached. ** Affects: zhcon (Ubuntu) Importance: Undecided Status: New ** Tags: console dbcs i18n japanese korean utf-8 -- 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 JIS support somewhat broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zhcon/+bug/998612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 73211] Re: MonoUralic contains incorrect encoding information
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 information > https://bugs.launchpad.net/bugs/73211 > You received this bug notification because you are a direct subscriber > of the bug. > -- MonoUralic contains incorrect encoding information https://bugs.launchpad.net/bugs/73211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 439697] Re: zhcon --utf8 truncates output on non-Chinese character
** 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 truncates output on non-Chinese character https://bugs.launchpad.net/bugs/439697 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 439697] [NEW] zhcon --utf8 truncates output on non-Chinese character
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 program output is not convertible from UTF-8 to the currently selected internal coding, zhcon silently truncates the output buffer, often discarding lots of following (potentially convertible) output. As an example: $ zhcon --utf8 # assume zhcon is now using GB2312 internal encoding $ env LC_ALL=ja_JP.UTF-8 ls --help # note that output is strangely truncated after a few lines Really something more sensible should be done, such as converting untranslatable characters to '?'. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: zhcon 1:0.2.6-6ubuntu1 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zhcon Uname: Linux 2.6.25-20090223.1.olpc.69098d87d56945c i586 ** Affects: zhcon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- zhcon --utf8 truncates output on non-Chinese character https://bugs.launchpad.net/bugs/439697 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438413] Re: init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000)
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)
https://bugs.launchpad.net/bugs/438413
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438413] [NEW] 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.) Also, the Linux console shows 16 colors, not the 8 suggested by . Since the bold attribute (which triggers the brighter color set for foreground colors) and the blink attribute (which triggers the brighter color set for background colors on the framebuffer console with a 256-position font) are not listed in , applications get all sorts of nasty surprises when they redefine colors and then use them in combination with these attributes. ProblemType: Bug Architecture: i386 Dependencies: DistroRelease: Ubuntu 9.04 Package: ncurses-term 5.7+20090207-1ubuntu1 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ncurses Uname: Linux 2.6.25-20090223.1.olpc.69098d87d56945c i586 ** Affects: ncurses (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000) https://bugs.launchpad.net/bugs/438413 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438413] Re: init_color (and the capability) for terminal type "linux" fails when red, green and/or blue is set to the maximum value (1000)
** 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" fails when red, green and/or blue is set to the maximum value (1000) https://bugs.launchpad.net/bugs/438413 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 437314] Re: SGR handling is broken
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 437314] [NEW] SGR handling is broken
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.3.3-5ubuntu4 findutils 4.4.0-2ubuntu4 libc6 2.9-4ubuntu6.1 DistroRelease: Ubuntu 9.04 Package: bogl-bterm 0.1.18-2ubuntu4 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bogl Uname: Linux 2.6.25-20090223.1.olpc.69098d87d56945c i586 ** Affects: bogl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 73211] Re: MonoUralic contains incorrect encoding information
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. > Means, you will need to explicitly choose the font if you want to > display documents with the broken encoding. > > ** Tags added: pet-bug > > -- > MonoUralic contains incorrect encoding information > https://bugs.launchpad.net/bugs/73211 > You received this bug notification because you are a direct subscriber > of the bug. > -- MonoUralic contains incorrect encoding information https://bugs.launchpad.net/bugs/73211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 73211] Re: MonoUralic contains incorrect encoding information
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? > > ** Changed in: ttf-uralic (Ubuntu) > Status: In Progress => Incomplete > > -- > MonoUralic contains incorrect encoding information > https://bugs.launchpad.net/bugs/73211 > You received this bug notification because you are a direct subscriber > of the bug. > -- MonoUralic contains incorrect encoding information https://bugs.launchpad.net/bugs/73211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73211] Re: MonoUralic contains incorrect encoding information
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://bugs.launchpad.net/bugs/73211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 261216] [NEW] symbol '_gotoxy' in /usr/lib/bcc/libdos.a should be exported to match
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:
undefined symbol: _gotoxy
Upon inspection of the library we see why:
$ nm86 /usr/lib/bcc/libdos.a | fgrep -i gotoxy
t _gotoxy
0004 a gotoxy.off
The symbol '_gotoxy' is defined as non-exported code (t) rather than
exported code (T)... maybe there is a missing 'extern' somewhere?
-- System Information:
Debian Release: lenny/sid
APT prefers hardy-updates
APT policy: (500, 'hardy-updates'), (500, 'hardy-security'), (500,
'hardy-backports'), (500, 'hardy')
Architecture: i386 (i686)
Kernel: Linux 2.6.20-16-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bcc depends on:
ii bin86 0.16.17-2ubuntu1 16-bit x86 assembler and loader
ii libc6 2.7-10ubuntu3GNU C Library: Shared libraries
Versions of packages bcc recommends:
ii elks-libc 0.16.17-2ubuntu1 16-bit x86 C library and include f
-- no debconf information
** Affects: linux86 (Ubuntu)
Importance: Undecided
Status: New
--
symbol '_gotoxy' in /usr/lib/bcc/libdos.a should be exported to match
https://bugs.launchpad.net/bugs/261216
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73211] Re: MonoUralic contains incorrect encoding information
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 you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 73211] Re: MonoUralic contains incorrect encoding information
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 perhaps, to display those characters even when the rest of the page is shown in monouralic.) furthermore some special characters are incorrectly displayed as cyrillic on pages using the monouralic font in firefox. for example, the "dagger" character (utf-8 %E2%80%A0, U+2020) is incorrectly displayed as a modified cyrillic Ka. note: all tests were done on utf-8 encoded pages where firefox was correctly detecting the encoding and characters from other parts of unicode were displayed correctly (in different fonts, of course). On 9/20/07, Arne Goetje <[EMAIL PROTECTED]> wrote: > I have reencoded the font (attached). > > Could you please try if all the characters show correctly in CP1251 encoding? > The font is modified CP1251 according to uralic needs. > > If this works, I will create a second font for Unicode. > However, that character mappings will be different and webpages and > documents, which are in the modified CP1251 encoding will not work. > > For testing, please remove the ttf-uralic package. Then copy the attached > font to ~/.fonts/ and run > fc-cache -fv ~/.fonts/ > After that: > xset fp rehash > > Then test with your favorite application / document. > > ** Attachment added: "MonoUralic.ttf" >http://launchpadlibrarian.net/9435247/MonoUralic.ttf > > -- > MonoUralic contains incorrect encoding information > https://bugs.launchpad.net/bugs/73211 > You received this bug notification because you are a direct subscriber > of the bug. > -- MonoUralic contains incorrect encoding information https://bugs.launchpad.net/bugs/73211 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 73211] Re: MonoUralic contains incorrect encoding information
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: > - > Additional letters > > The encoding of the fonts is based on the model of the Cyrillic Asian > encoding. The Russian alphabet occupies the place of > the Latin-1 supplement in the Western (Windows CP 1252) encoding and its > own Unicode positions in the Cyrillic (CP 1251) encoding. Additional > Uralic letters can be found in three places - instead of additional > characters in the Western encoding, instead of additional characters in > the Cyrillic encoding and in their own Unicode positions (with the > exceptions of those letters that are not found in this standard). > Existing Mari and Udmurt fonts were taken into consideration while > distributing positions, but incorporating their encodings did not prove > possible. Eventually, Udmurt fonts were used as the starting point. See > the test page for details. > > > > These fonts are for Uralic languages only! So, don't use these fonts for any > other purpose. > I will nevertheless contact upstream and propose a fix. IMHO the fonts have > been wrongfully encoded and are therefor broken. Even when used in a Unicode > environment, additional Cyrillic characaters should only show up in the > U+00A0 - U+00BF range. At least, that's the mapping of CP1251 to Unicode. > > ** Changed in: ttf-uralic (Ubuntu) > Assignee: (unassigned) => Arne Goetje >Status: Incomplete => In Progress > > -- > MonoUralic contains incorrect encoding information > https://bugs.launchpad.net/bugs/73211 > You received this bug notification because you are a direct subscriber > of the bug. > -- MonoUralic contains incorrect encoding information https://bugs.launchpad.net/bugs/73211 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93885] Re: It's completely broken: missing org/mozilla/javascript/tools/shell/Main
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.runtime.SystemClassLoader{urls=[file:/usr/share/java/js.jar],
parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}
at java.net.URLClassLoader.findClass(libgcj.so.70)
at gnu.gcj.runtime.SystemClassLoader.findClass(libgcj.so.70)
at java.lang.ClassLoader.loadClass(libgcj.so.70)
at java.lang.ClassLoader.loadClass(libgcj.so.70)
at gnu.java.lang.MainThread.run(libgcj.so.70)
$ unzip -l /usr/share/java/js.jar | fgrep -i tools # no output...
$ apt-cache show rhino
Package: rhino
Priority: optional
Section: interpreters
Installed-Size: 584
Maintainer: Ubuntu Core Developers <[EMAIL PROTECTED]>
Original-Maintainer: Debian Java Maintainers
Architecture: all
Version: 1.6.R5-0ubuntu1
Depends: java-gcj-compat | java1-runtime | java2-runtime
Suggests: rhino-doc
Filename: pool/main/r/rhino/rhino_1.6.R5-0ubuntu1_all.deb
Size: 487672
MD5sum: c6ff406eee7b3351d6b1e50d74299559
SHA1: 8e1a96115f0cfc79e803e8aa5b82941ec817d752
SHA256: 4947c8359209281df1f7f53c2bd0277293b1adf49e055370130b19c7e0300bfd
Description: JavaScript engine written in Java
Rhino is an open-source implementation of JavaScript written
entirely in Java. It is typically embedded into Java applications
to provide scripting to end users.
Bugs: mailto:[EMAIL PROTECTED]
Origin: Ubuntu
--
It's completely broken: missing org/mozilla/javascript/tools/shell/Main
https://launchpad.net/bugs/93885
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73211] Re: MonoUralic contains incorrect encoding information
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
[Bug 73211] MonoUralic contains incorrect encoding information
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 package installs MonoUralic as a replacement for "Courier", which many applications (including e.g. Firefox) depend on for correct Unicode display. other fonts in the ttf-uralic package appear to have the same bug. this means that if ttf-uralic is installed, then e.g. French webpages become unreadably broken. ** Affects: ttf-uralic (Ubuntu) Importance: Undecided Status: Unconfirmed -- 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
Re: [Bug 56633] Re: buffer overrun in repr() for unicode strings
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 installed: python2.4 2.4.2-0ubuntu3 On Tue, 2006-10-03 at 01:54 +, Kees Cook wrote: > I've got debdiffs built, and will be sending to pitti shortly. > -- 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
[Bug 56633] Re: [Bug 56633] Re: buffer overrun in repr() for unicode strings
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"\U0001" * 39 +u"\u" * 4096)) ==(repr(u"\U0001" * 39 + u"\u" * 4096))' *** glibc detected *** python2.4: realloc(): invalid next size: 0x081a2628 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0xb7e0d38a] /lib/tls/i686/cmov/libc.so.6(__libc_realloc+0xff)[0xb7e0dcbf] python2.4(_PyString_Resize+0x91)[0x8084bb1] python2.4[0x809c0c8] python2.4(PyObject_Repr+0x65)[0x807edc5] python2.4(PyEval_EvalFrame+0x4801)[0x80b8941] python2.4(PyEval_EvalCodeEx+0x839)[0x80b9fc9] python2.4(PyEval_EvalCode+0x57)[0x80ba037] python2.4(PyRun_SimpleStringFlags+0xa8)[0x80dd3d8] python2.4(Py_Main+0x684)[0x8055884] python2.4(main+0x22)[0x80550f2] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc)[0xb7dba8cc] python2.4[0x8055041] === Memory map: 08048000-0812 r-xp 08:03 623527 /usr/bin/python2.4 0812-08141000 rw-p 000d8000 08:03 623527 /usr/bin/python2.4 08141000-081b8000 rw-p 08141000 00:00 0 [heap] b7b0-b7b21000 rw-p b7b0 00:00 0 b7b21000-b7c0 ---p b7b21000 00:00 0 b7cc3000-b7ccd000 r-xp 08:03 2285687/lib/libgcc_s.so.1 b7ccd000-b7cce000 rw-p 9000 08:03 2285687/lib/libgcc_s.so.1 b7ceb000-b7d1e000 r--p 08:03 82634 /usr/lib/locale/en_US.utf8/LC_CTYPE b7d1e000-b7d21000 r-xp 08:03 635852 /usr/lib/python2.4/lib-dynload/_locale.so b7d21000-b7d22000 rw-p 3000 08:03 635852 /usr/lib/python2.4/lib-dynload/_locale.so b7d22000-b7da5000 rw-p b7d22000 00:00 0 b7da5000-b7ed2000 r-xp 08:03 2362694/lib/tls/i686/cmov/libc-2.4.so b7ed2000-b7ed4000 r--p 0012c000 08:03 2362694/lib/tls/i686/cmov/libc-2.4.so b7ed4000-b7ed6000 rw-p 0012e000 08:03 2362694/lib/tls/i686/cmov/libc-2.4.so b7ed6000-b7ed9000 rw-p b7ed6000 00:00 0 b7ed9000-b7efd000 r-xp 08:03 2363095/lib/tls/i686/cmov/libm-2.4.so b7efd000-b7eff000 rw-p 00023000 08:03 2363095/lib/tls/i686/cmov/libm-2.4.so b7eff000-b7f01000 r-xp 08:03 2363110 /lib/tls/i686/cmov/libutil-2.4.so b7f01000-b7f03000 rw-p 1000 08:03 2363110 /lib/tls/i686/cmov/libutil-2.4.so b7f03000-b7f04000 rw-p b7f03000 00:00 0 b7f04000-b7f06000 r-xp 08:03 2363094/lib/tls/i686/cmov/libdl-2.4.so b7f06000-b7f08000 rw-p 1000 08:03 2363094/lib/tls/i686/cmov/libdl-2.4.so b7f08000-b7f17000 r-xp 08:03 2363105 /lib/tls/i686/cmov/libpthread-2.4.so b7f17000-b7f19000 rw-p f000 08:03 2363105 /lib/tls/i686/cmov/libpthread-2.4.so b7f19000-b7f1b000 rw-p b7f19000 00:00 0 b7f31000-b7f38000 r--s 08:03 2130376 /usr/lib/gconv/gconv-modules.cache b7f38000-b7f3a000 rw-p b7f38000 00:00 0 b7f3a000-b7f53000 r-xp 08:03 376899 /lib/ld-2.4.so b7f53000-b7f55000 rw-p 00018000 08:03 376899 /lib/ld-2.4.so bff0d000-bff23000 rw-p bff0d000 00:00 0 [stack] e000-f000 ---p 00:00 0 [vdso] Aborted $ On 8/25/06, Matthias Klose <[EMAIL PROTECTED]> wrote: > fixed in 2.4.3-8ubuntu1 > > > ** Changed in: python2.4 (Ubuntu) > Assignee: (unassigned) => Matthias Klose >Status: Confirmed => Fix Released > > -- > buffer overrun in repr() for unicode strings > https://launchpad.net/bugs/56633 > -- 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
[Bug 56633] Re: [Bug 56633] Re: buffer overrun in repr() for unicode strings
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 > > http://sourceforge.net/tracker/index.php?aid=1541585&group_id=5470&atid=305470&func=detail > > ** Also affects: python (upstream) via > > http://sourceforge.net/tracker/index.php?aid=1541585&group_id=5470&atid=305470&func=detail >Importance: Unknown >Status: Unknown > > -- > buffer overrun in repr() for unicode strings > https://launchpad.net/bugs/56633 > -- 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
[Bug 56633] Re: buffer overrun in repr() for unicode strings
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
[Bug 56633] Re: buffer overrun in repr() for unicode strings
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-bugs
[Bug 56633] buffer overrun in repr() for unicode strings
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 is fixed by a change to unicodeobject.c. in the process of fixing it i also found and fixed another bug in repr() on UCS-4 python builds -- previously paired unicode surrogates were being repr()'ed as a single "character" even though they are not treated as such by a UCS-4 python build -- i.e. eval(repr(u'\ud800\udc00')) != u'\ud800\udc00' in an unpatched UCS-4 build. Package: python2.4 Version: 2.4.3-7ubuntu2 Severity: important when i run this command: python -c "repr(u'\u24ea\u059c\u200a\U0001d77e\uff07\u202f\u0747\u202f \U0001d56b\U0001d5b9\U0001d4e9\u20052\u14bf\U0001d7f8\u200a\U0001d795 \U0001d6e7Z\u2006\u2002\U0001d50a\uff27\u13c0\u2000\uff16\u0411\uff16 \U0001d7e7\uff4c\u2006\u2001\ufe39\u2008\u0313]\u2008\u3014\u3015')" python aborts with the following backtrace and memory dump: *** glibc detected *** python: realloc(): invalid next size: 0x081521e8 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0xb7e8acd4] /lib/tls/i686/cmov/libc.so.6(__libc_realloc+0xff)[0xb7e8cc5f] python(_PyString_Resize+0x80)[0x8082b4b] python[0x80991f7] python(PyObject_Repr+0x58)[0x807d1fd] python(PyEval_EvalFrame+0x4b37)[0x80b5270] python(PyEval_EvalCodeEx+0x836)[0x80b65d6] python(PyEval_EvalCode+0x57)[0x80b6640] python(PyRun_SimpleStringFlags+0xa8)[0x80d8b7c] python(Py_Main+0x685)[0x8055862] python(main+0x22)[0x80550e2] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd8)[0xb7e378b8] python[0x8055041] === Memory map: 08048000-0811a000 r-xp 08:03 622736 /usr/bin/python2.4 0811a000-0813b000 rw-p 000d1000 08:03 622736 /usr/bin/python2.4 0813b000-081b5000 rw-p 0813b000 00:00 0 [heap] b7c0-b7c21000 rw-p b7c0 00:00 0 b7c21000-b7d0 ---p b7c21000 00:00 0 b7d4-b7d4a000 r-xp 08:03 376899 /lib/libgcc_s.so.1 b7d4a000-b7d4b000 rw-p 9000 08:03 376899 /lib/libgcc_s.so.1 b7d68000-b7d9b000 r--p 08:03 82634 /usr/lib/locale/en_US.utf8/LC_CTYPE b7d9b000-b7d9e000 r-xp 08:03 625529 /usr/lib/python2.4/lib-dynload/_locale.so b7d9e000-b7d9f000 rw-p 3000 08:03 625529 /usr/lib/python2.4/lib-dynload/_locale.so b7d9f000-b7e22000 rw-p b7d9f000 00:00 0 b7e22000-b7f51000 r-xp 08:03 66543 /lib/tls/i686/cmov/libc-2.4.so b7f51000-b7f53000 r--p 0012e000 08:03 66543 /lib/tls/i686/cmov/libc-2.4.so b7f53000-b7f55000 rw-p 0013 08:03 66543 /lib/tls/i686/cmov/libc-2.4.so b7f55000-b7f58000 rw-p b7f55000 00:00 0 b7f58000-b7f7c000 r-xp 08:03 66547 /lib/tls/i686/cmov/libm-2.4.so b7f7c000-b7f7e000 rw-p 00023000 08:03 66547 /lib/tls/i686/cmov/libm-2.4.so b7f7e000-b7f8 r-xp 08:03 68161 /lib/tls/i686/cmov/libutil-2.4.so b7f8-b7f82000 rw-p 1000 08:03 68161 /lib/tls/i686/cmov/libutil-2.4.so b7f82000-b7f83000 rw-p b7f82000 00:00 0 b7f83000-b7f85000 r-xp 08:03 66546 /lib/tls/i686/cmov/libdl-2.4.so b7f85000-b7f87000 rw-p 1000 08:03 66546 /lib/tls/i686/cmov/libdl-2.4.so b7f87000-b7f96000 r-xp 08:03 68156 /lib/tls/i686/cmov/libpthread-2.4.so b7f96000-b7f98000 rw-p f000 08:03 68156 /lib/tls/i686/cmov/libpthread-2.4.so b7f98000-b7f9a000 rw-p b7f98000 00:00 0 b7fb-b7fb7000 r--s 08:03 2130015/usr/lib/gconv/gconv-modules.cache b7fb7000-b7fb9000 rw-p b7fb7000 00:00 0 b7fb9000-b7fd2000 r-xp 08:03 2737127/lib/ld-2.4.so b7fd2000-b7fd4000 rw-p 00018000 08:03 2737127/lib/ld-2.4.so bf99b000-bf9b3000 rw-p bf99b000 00:00 0 [stack] e000-f000 ---p 00:00 0 [vdso] Aborted -- System Information: Debian Release: testing/unstable APT prefers edgy-updates APT policy: (500, 'edgy-updates'), (500, 'edgy-security'), (500, 'edgy-backports'), (500, 'edgy') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-5-386 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages python2.4 depends on: ii libbz2-1.01.0.3-3high-quality block-sorting file co ii libc6 2.4-1ubuntu8 GNU C Library: Shared libraries ii libdb4.4 4.4.20-6 Berkeley v4.4 Database Libraries [ ii libncurses5 5.5-2ubuntu1 Shared libraries for terminal hand ii libncursesw5 5.5-2ubuntu1 Shared libraries for terminal hand ii libreadline5 5.1-7build1GNU readline and history libraries ii libssl0.9.8 0.9.8b-2build1 SSL shared libraries ii mime-support 3.36-1 MIME files 'mime.types' & 'mailcap ii python2.4-minimal 2.4.3-7ubuntu2 A minimal subset of the Python lan python2.4 recommends no packages. -- no debconf i
