GOWrite 2.3.48

[lpaatero]

GOWrite 2.3.48 adds Japanese translation and updates Japanese Help, both contributed by Shunichi Akiba and his team (thank you!).

Other changes

* Version resets default SGF character set to UTF-8.
* Default character set is now used always when saving file. So original character set is ignored.

- Lauri

[johny]

Just tried install the rpm package on ubuntu 12.04:
1. gunzip gowrite-2.3.48-1.noarch.rpm.gz
2. sudo apt-get install alien dpkg-dev debhelper build-essential
3. sudo alien gowrite-2.3.48-1.noarch.rpm
4. sudo dpkg -i gowrite_2.3.48-2_all.deb

Works like a charm.

[johny]

Problem is, if I open a sgf record in the board, the comment (written in Chinese) is displayed as unreadable. Is there an option to adjust the comment display language?

[johny]

Just want to point out that, if we run gowrite2 directly from the command line in ubuntu 12.04, there would be some error msg like:
johny@johny:~$ gowrite2
starting GO Write 2...
/opt/gowrite2/gowrite2: 34: [: -a: unexpected operator
/opt/gowrite2/gowrite2: 37: [: -a: unexpected operator

The error is not fatal, and the application runs well.

Still, the error msg can be eliminated by the following simple fix:
johny@johny:/opt/gowrite2$ diff gowrite2.org gowrite2
1c1
< #!/bin/sh
---
> #!/bin/bash

[lpaatero]

Hi,

Could you send me the sgf with unreadable chinese?
Many sgf files are missing character encoding and gowrite attempts to guess the coding. It is likely that this guessing is not working in this case.

I will update the starting script in 3.0.x version, thanks for point this out.


regards
Lauri

[johny]

Lauri,

I have sent you an email with the Chinese commented sgf files attached. Please let me know if you can't received my email.

Thanks,
johny

[lpaatero]

I got the mail, thanks.

In this case there is easy solution:

Install development version 3.0.10, it is available in downloads http://gowrite.net/GOWrite2_download.html.
These development versions are now getting more stable, so there should not be risk in trying them.

If you see any files that do not open correctly with 3.0 version, let me know.

regards
Lauri

[johny]

Lauri,

I tried the development version 3.0.10, and played with the SGF options, but it seems not working to solve the comment language problem.

I have sent another email with my screen shots attached. Please have a look at them.

Thanks,
johny

[lpaatero]

Thank you.

It seems gowrite is behaving bit randomly. Its character set detection algorithm does not find any good hints, and resulting character set is pretty random.

I will look at this; it seems difficult case, so I cannot promise quick solution.

As work-around, you can use File -> Open, and there select character set GB18030.

[johny]

Thank you, Lauri.

Yes, your walk-around works for me. I didn't notice there is the character set option when a file is opened.

Thanks!
johny

[lpaatero]

Hi,

There is now test -version for better character set recognition:
http://gowrite.net/download/gowrite-3.0 ... rch.rpm.gz

It is probably almost always better than 3.0.10 at guessing character set.

Let me know how well it works.

regards
Lauri

[johny]

Hi Lauri,

Tried your test version of gowrite-3.0.11-1.noarch.rpm. However, the "Auto Character Set" (in File -> Open dialog) doesn't work well with my commented sgf file. I still have to explicitly set it to GBK to display the Chinese comments.

Am I missing anything?

Update:
Found the cause why it was not working --- I have to remove the hidden directory ".gowrite", which was left over by the previous version(s) of gowrite2. After removing this hidden directory from my home directory, and give it a fresh restart (the hidden directory will be re-created by the new version 3.0.11-1) by running the script /opt/gowrite2/gowrite2, the "Auto Character Set" (in File -> Open dialog) feature works very well to recognize the Chinese comments in my sgf files.

Thanks for your efforts in improving gowrite2, and congratulations on your success in fixing this issue!
johny

[lpaatero]

Thanks for pointing out .gowrite issue.
It is probably doe to sharing (somewhat incompatible) settings file with gowrite 2.0.
I will do something about this.

- Lauri