GnuCash
Contact   Instructions
Bug 797295 - problems with entering swedish åäö in company address
Summary: problems with entering swedish åäö in company address
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: General (show other bugs)
Version: 3.5
Hardware: PC Windows
: Normal minor
Target Milestone: ---
Assignee: general
QA Contact: general
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-29 08:47 EDT by Anders Lorentzson
Modified: 2019-07-30 17:11 EDT (History)
5 users (show)

See Also:


Attachments
Business Options typed with Swedish Keyboard (14.59 KB, image/png)
2019-07-07 18:33 EDT, John Ralls
no flags Details

Description Anders Lorentzson 2019-06-29 08:47:35 EDT
When I try to change my company address it just disappears when I use Swedish characters e.g.

Sjöbacken 1
514 95 GRIMSÅS

If I instead change it to:

Sjobacken 1
514 95 GRIMSAS 

it beahves as it should, and I can change the address. So it's using dots and rings above characters that confuses the program.

Anders Lorentzson
Comment 1 Christopher Lam 2019-06-29 09:36:18 EDT
This is probably fixed in recent Windows builds. Suggest wait until 3.6 is released and try again.
Comment 2 Christopher Lam 2019-06-29 10:11:30 EDT
Alternatively try a recent development build https://code.gnucash.org/builds/win32/maint/
Comment 3 John Ralls 2019-06-29 11:14:08 EDT
Anders, what version of Windows are you running?
Comment 4 Anders Lorentzson 2019-06-29 15:49:17 EDT
Windows 10 version:1903
Comment 5 John Ralls 2019-06-29 16:08:59 EDT
I don't have any trouble typing Swedish characters into a register description field or an entry in an Account Edit dialog box using GnuCash 3.5 on Win10. That's with a US keyboard and the built-in Swedish keyboard layout. If you have a hardware Swedish keyboard, that's not something I can test, nor do I know how to get it to work with Gtk.
Comment 6 Anders Lorentzson 2019-07-01 05:42:37 EDT
I have no problems using åäö in register description fields. It's just when I tried to change my Companys address it's misbehaving.
Comment 7 Christopher Lam 2019-07-01 10:03:46 EDT
@Anders have you tried the latest 3.6 release? It may have fixed this problem.
Comment 8 Anders Lorentzson 2019-07-06 10:29:46 EDT
Now I have tried the 3,6 release with the same result. It can't accept å, ä and ö.
It's in this section:

"Business Book Options Tab
Figure 10.16. The Book Options window, Business tab 

The Book Options window, Business tab


The Business tab allows you to enter values that are in turn used by the business features of GnuCash:

Company Name
The name of the company is used in many reports."

It's kind of annoying because when I print out my invoices, the company address is wrong.

Anders
Comment 9 John Ralls 2019-07-07 18:33:14 EDT
Created attachment 373317 [details]
Business Options typed with Swedish Keyboard

It works OK for me in Company Info, see the screen shot.
Comment 10 Anders Lorentzson 2019-07-09 07:29:38 EDT
Very strange! 
I can change company name and then using åäö, that works fine. But I can't change in company address. I even made a totally new company with Swedish characters and the company name was saved but the address wasn't. Then I thought about Environment, the last couple of times I have updated GnuCach I have it in Swedish without changing: 

[Variables]
LANG=Swedish_Sweden
LANGUAGE=sv

Doing this it still didn't work to change the company address. Then by sheer luck I pressed enter (carriage return) after GRIMSÅS and now I finally have the correct address to my company!
Comment 11 John Ralls 2019-07-09 10:00:40 EDT
Is this about typing or about saving?

I understood it to be about typing, that ö and Å don't appear when you type them. Is the problem really that they enter OK but don't get saved if you close the dialog and then reopen it or run an invoice? And you've now learned that putting a newline on the second line causes them to be saved?

How are you entering the accented characters?
Comment 12 Anders Lorentzson 2019-07-10 15:14:56 EDT
It was when I pressed OK or save that everything just dissappeard if there was Swedish characters in the address field. (No problems entering the characters.) Without Swedish characters it behaved as expected and saved even without a carriage return. So some kind of bug is still there. But I'm OK now since the work around.

Anders
Comment 13 John Ralls 2019-07-11 18:41:22 EDT
Ah, I hadn't understood that the text entered OK but the field blanks after saving. I'm able to replicate the problem now, but not the work-around. It disappears for me regardless.

The string *is* getting saved, though, I can see it when I look at the XML file in a terminal.

I can also replicate the problem on MacOS.
Comment 14 John Ralls 2019-07-11 20:42:49 EDT
And fixed. You can use tomorrow's nightly from https://code.gnucash.org/builds/win32/maint or wait for GnuCash 3.7.
Comment 15 Geert Janssens 2019-07-30 11:08:55 EDT
Do you want the OP to test the change before closing or forgot to close ?
Comment 16 Anders Lorentzson 2019-07-30 13:00:39 EDT
Ok I'm new to this, sorry :-) 
I am ok that the Bug-report is closed and I don't need to test the change since it works for me now and John Ralls has promised it to be solved in 3.7
Comment 17 Geert Janssens 2019-07-30 14:29:47 EDT
(In reply to Anders Lorentzson from comment #16)
> Ok I'm new to this, sorry :-) 
> I am ok that the Bug-report is closed and I don't need to test the change
> since it works for me now and John Ralls has promised it to be solved in 3.7

Thanks for your reply.

This question was really meant for John, I should have made the more clear.

For your info, in the question "OP" is shorthand for "original poster", meaning you. We devs typically either close a bug directly if we're confident it's fixed or we ask users to verify a fix if we're not that confident. That is typically indicated by setting the bug's status to "NEEDINFO". As John didn't do so I simply asked for his intention.
Comment 18 John Ralls 2019-07-30 17:11:13 EDT
I'd just failed to mark it resolved when I reported that I'd fixed it.

Note You need to log in before you can comment on or make changes to this bug.