David Hampton <[EMAIL PROTECTED]> writes:
> On Thu, 2005-10-13 at 22:54 +0200, Didier Vidal wrote:
>
>> If this is true, that means that the problems lies in the way messages
>> are passed to gnome. Something should be done to convert them from the
>> locale's charmap to utf-8 before displaying th
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
Le dim 16/10/2005 à 12:40, Neil Williams a écrit :
> On Thursday 13 October 2005 9:00 pm, Neil Williams wrote:
> > It's now fine. Problem solved. Account summary and reports are fine - no
> > pango warnings, no missing currency symbols or numbers and no funny
> > prefixes.
>
> Forget that. It's st
On Thursday 13 October 2005 9:00 pm, Neil Williams wrote:
> It's now fine. Problem solved. Account summary and reports are fine - no
> pango warnings, no missing currency symbols or numbers and no funny
> prefixes.
Forget that. It's still broken.
Despite setting LANG=en_GB.UTF-8 in ~/.bashrc and
On Thu, 2005-10-13 at 22:54 +0200, Didier Vidal wrote:
> If this is true, that means that the problems lies in the way messages
> are passed to gnome. Something should be done to convert them from the
> locale's charmap to utf-8 before displaying them.
Why are we reading ISO-8859 characters in th
I think reproduced the problem.
Although I do not have the warnings (maybe there is no trace in my
version of pango), I get display errors.
The problem apears if I use the pound as currency with the en_GB locale.
The explanation would be the following:
gnucash attempts to display the pound symbo
On Thu, 2005-10-13 at 21:00 +0100, Neil Williams wrote:
> The default isn't to use UTF-8, is this something we need to document
> somewhere? (apart from the list archive).
>
> The section in GNOME2_STATUS can be removed whenever anyone is next editing
> it.
Or diminished, but it'd be nice to kn
On Thursday 13 October 2005 2:57 pm, Josh Sled wrote:
> On Thu, 2005-10-13 at 09:06 +0100, Neil Williams wrote:
> > It's more than just warnings to the console. Now that I've been building
> > updated trees and testing within G2 regularly, I can report that these
> > pango errors are preventing G2
I haven't seen any of these errors on FC3, either.
-derek
Didier Vidal <[EMAIL PROTECTED]> writes:
> On Fedora 2, I don't see any of these warnings. Wheter the locale is
> fr_FR or fr_FR.utf8. No problem either with en_GB. Pango version is
> 1.4.1.
>
> Didier.
>
> Le jeu 13/10/2005 à 15:57, Josh
On Fedora 2, I don't see any of these warnings. Wheter the locale is
fr_FR or fr_FR.utf8. No problem either with en_GB. Pango version is
1.4.1.
Didier.
Le jeu 13/10/2005 à 15:57, Josh Sled a écrit :
> On Thu, 2005-10-13 at 09:06 +0100, Neil Williams wrote:
> > It's more than just warnings to the
On Thu, 2005-10-13 at 09:06 +0100, Neil Williams wrote:
> It's more than just warnings to the console. Now that I've been building
> updated trees and testing within G2 regularly, I can report that these pango
> errors are preventing G2 from displaying any *numbers* or *currency symbols*
> in th
Just a heads-up on the pango problems reported previously and highlighted in
GNOME2_STATUS.
It's more than just warnings to the console. Now that I've been building
updated trees and testing within G2 regularly, I can report that these pango
errors are preventing G2 from displaying any *numbers
12 matches
Mail list logo
