Pango and Debian

[Neil Williams]

On Sunday 16 October 2005 11:49 am, you wrote:
> The problem is that ~/.bashrc is not used for your (non-bash...) X
> session. If you use change the command for the menu entry to do
> something as "LANG=en_GB.UTF-8 gnucash"

Not accepted. I cannot specify en_GB.UTF-8 in the icon advanced properties.

It sets it as a secondary option, then when I remove the first one (en_GB), it 
ignores that and resets en_GB anyway.

No matter how I try it, the icon refuses to allow en_GB.UTF-8 or en_GB.utf-8.

I've even removed the icon from the panel, created a new one and set the 
language - it's ignored. When you view the properties of the icon, it's just 
en_GB and the bug reappears. GnuCash simply does not receive the UTF-8 via 
the icon.

It works from icons on the desktop, but not from the Gnome panel.

This is a completely default Gnome install for the en_GB language - I was not 
offered or allowed to set UTF-8 anywhere in the setup - no other app is 
affected so if gnucash requires en_GB.UTF-8 then it will have to be set 
specifically for gnucash. Currently, gnucash is either ignoring or not 
requesting that data.

I still think this is a bug in gnucash relating to the pango implementation, 
not just a problem with this installation.

Interestingly, even if I go for the UGLY option and enable "Run in terminal", 
the terminal window appears, gnucash runs but the window fills up with 
thousands of pango errors and gnucash STILL refuses to display the numbers or 
currency symbol.

Every terminal window receives the correct language so gnucash really does 
seem to be not listening.

> or set LANG in something that 
> gets processed for logins via the desktop managers (IIRC this was
> problematic some time ago and /etc/environ was more or less the only
> really safe bet), you'd probably do better.

So this needs to be documented somewhere? The icon settings are part of the 
tarball - don't package maintainers need to know this? We don't want users 
coming up against this as a bug.

> This is a private mail due to possible lack of relevance for the list,
> but feel free to do quote it around and stuff.

I think it should still go on the list. It is relevant because we are 
preparing for a release and this would be a release critical bug.

BTW. When I DO set .UTF-8, I now get bugs in manpages!

-- 

Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20051016/36e40f4a/attachment.bin