#30 Using Kanji Stroke Order Font leads to unreadable kanji

open
5
2012-09-18
2010-01-24
runiq
No

Although I'm not really satisfied with the previous comment's tone, I second the notion for using a separate font for the kanji lookup display. I don't know if it's intentional, but as soon as I have the Kanji Stroke Order Font (http://sites.google.com/site/nihilistorguk – shows small numbers next to the lines) installed, not only the big single kanji in the lookup display uses the font, the first lines in each result uses it as well. (See screenshot on – both kanji and hiragana use it). This makes kanji with lots of strokes unreadable even with the biggest font size.

When I have the Kanji Stroke Order Font (http://sites.google.com/site/nihilistorguk) installed, gwaei shows small numbers next to the lines in a kanji in the kanji lookup sidebar, which in itself is a very useful feature. However, the stroke order font is used for the first lines in each search result as well, which results in nigh unreadable kanji, even when using the biggest font size available (see attached screenshot).

In my opinion, the stroke order font should solely be used for the kanji lookup display.

Discussion

  • runiq

    runiq - 2010-01-24
     
  • runiq

    runiq - 2010-01-24

    Whoops, I forgot to delete the draft I used for this bug report. :( Disregard the first paragraph, please!

     
  • Zachary Dovel

    Zachary Dovel - 2010-01-25

    I looked at the screenshot and it shouldn't be doing that runiq, It's definitely a bug. Though I am not sure exactly why it is only doing it on your setup.

    I fell behind on releasing a new gWaei which was planned for around the 5th and it has stayed in that state. I'll see if I can reproduce when I get some free time.

    I'm switching over the document front from defaulting to Sans to using the gnome global font setting found in gnome-appearance-properties so users have more control. But the change is still in sitting in the git repo.

    I am not sure what you mean by previous comment? This looks like a fresh bug I think.

     
  • runiq

    runiq - 2010-01-25

    Yeah, I initially wanted to add this as a comment to another ticket instead of opening up a new one, that's why I said to disregard the first paragraph.

    I'll go ahead and try the git version, then. Take your time with releasing :)

     
  • Zachary Dovel

    Zachary Dovel - 2010-01-26

    Quick question. Are you using Ubuntu, and did you install the fonts using a repository? I want to be bale to mimic your setup as closely as possible.

     
  • runiq

    runiq - 2010-01-26

    I'm using Arch Linux, gwaei 1.2.1, and installed this http://aur.archlinux.org/packages.php?ID=31738 package for the font. It basically just puts the ttf files in their proper directories and updates the font cache.

     
  • runiq

    runiq - 2010-03-18

    Sorry it took me so long to come back to this, but the error also appears when using the git version.

     
  • Zachary Dovel

    Zachary Dovel - 2010-03-19

    Hrm, something is definitely very odd, runiq. I haven't seen the problem on Gentoo, Ubuntu, or Fedora. Are you a package maintainer runiq for Archlinux? Would you happen to have a machine I could ssh in on to test?

    Hrm. I just read the introduction on the Arch Linux webpage. I am thinking I might switch my netbook install to Archlinux from Gentoo so I don't have to compile on it anymore. Compiling everything on this machine is painful. :)

    One way or another, I will have this fixed in 1.3.1, but I am planning on releasing 1.3.0 in the next 24 hours to get it out and to try to get some more people reviewing the updates for bugs etc. If you are a package maintainer and you want a temporary fix through a patch, I would have the patch change line 2514 of main-interface-gtk.c from:
    gw_ui_set_tag_to_tagtable ("large", GW_TARGET_KANJI, "font", "KanjiStrokeOrders, serif 100");
    to:
    gw_ui_set_tag_to_tagtable ("large", GW_TARGET_KANJI, "font", "serif 100");
    This will remove the one and only direct reference in the program to KanjiStrokeOrders.

     
  • runiq

    runiq - 2010-03-19

    No, I'm unfortunately not a package maintainer, I just maintain the gwaei-git package in the AUR since yesterday (http://aur.archlinux.org/packages.php?ID=35619). If it works on any other machine/distribution, the issue has to be on my side. No SSH access though, since the only machine I'm using is my work/uni/all-in-one laptop machine :/

    Thanks for the patch, though, I'll apply it and see what happens. If that doesn't work, I guess I have to look around gconf settings some more. (I don't use gnome ATM.)

    Thanks for your consideration, btw! :)

     
  • Zachary Dovel

    Zachary Dovel - 2010-03-19

    I've had distro specific problems before, so I'm going to keep an eye out. They tend to point to real bugs in the code. Though they usually manifest themselves as crashes....

    I may actually switch to ArchLinux full time on my netbook anyway. I'm not going to get to installing it until after 1.3.0 releases, though. Fedora 13 was already pain in the butt enough to install for testing... :)

     
  • runiq

    runiq - 2010-03-19

    Haha, welcome on board then, glad to have you around. :)

    I just noticed that gwaei uses the proper fonts ("sans-serifed" kanji) in the "Kanji" and "Names" dictionaries, but not in the other dictionaries. Applying the patch didn't help either – as long as the Kanji Stroke Orders font is installed on my system, it is used.

     
  • Zachary Dovel

    Zachary Dovel - 2010-03-19

    Last question before I look at the problem first hand:

    What does "gconftool-2 -g /desktop/gnome/interface/document_font_name" read when you enter it is the console? There shouldn't be anywhere else in the program calling for a KanjiStokeOrders but that one line that I gave you.

     
  • runiq

    runiq - 2010-03-19

    I tried it with/without a changed line 2514 and with/without the Kanji Stroke Orders Font installed – the command always spits out "Sans 10".

    BTW, I'm sorry I didn't notice this earlier, but I made a mistake while changing the line you mentioned – something does happens when I change it and recompile gwaei: The Kanji Stroke Orders Font isn't used for the big kanji in the Kanji Lookup display – but it is still used for the search results in the dictionaries I already mentioned (see screenshot #2). Something's fishy here…

     
  • runiq

    runiq - 2010-03-19

    Screenshot #2 of gwaei after removing "KanjiStrokeOrders, " from line 2514 in main-interface-gtk.c

     
  • Zachary Dovel

    Zachary Dovel - 2010-03-19

    Yup, that is why I want to check it out first hand. There is no good reason for the program to be using KanjiStrokeOrders as your font. To make sure, I may do a search over all the source code files to make sure there isn't another reference to KanjiStrokeOrders somewhere else, too.

     
  • runiq

    runiq - 2010-03-20

    I just grepped through the freshly cloned source directory, and the only match that was found was the line you mentioned in main-interface-gtk.c:

    $ grep -Rn 'KanjiStrokeOrders' *
    src/main-interface-gtk.c:2514: gw_ui_set_tag_to_tagtable ("large", GW_TARGET_KANJI, "font", "KanjiStrokeOrders, serif 100");

     
  • Zachary Dovel

    Zachary Dovel - 2010-03-20

    Runiq, once I get Arch Linux installed on a partition I'll figure out the problem. I think there is no other way than to test it out directly. I should have the fix out in a week or 2. Maybe earlier.

     
  • runiq

    runiq - 2010-03-20

    No problem, I'm sorry if I was too pressing. Take your time. :)

     
  • Zachary Dovel

    Zachary Dovel - 2010-03-28

    Bah, sorry for another not-so-useful comment. In the git builds I have recently rewrote a lot of the font code. Also, you can manually set the font from the preferences now. Is the situation the same?

    I downloaded Arch Linux, but I haven't gotten to installing it yet.

     
  • Zachary Dovel

    Zachary Dovel - 2010-04-05

    Installed Arch Linux and did the testing. I can't seem to be able to find Kochi Substitute in the repos. Once it is manually installed, kanji stroke order no longer pops up in gWaei. runiq, you're going to have to find the baseline gothic ttf japanese font for Arch Linux and add it as a dependency. Otherwise, the system to grab at kanjistrokeorders because there is nothing else to use for truetype fonts. You could look at Togoshi or ipa fonts.

    kochi substitute link -> http://jaist.dl.sourceforge.jp/efont/5411/kochi-substitute-20030809.tar.bz2

    To try to combat this, I can try specifying Ipa/Togashi ahead of Sans, but if that problem is happening, it is most likely happening for other applications too, no?

     
  • runiq

    runiq - 2010-05-31

    First of all, the issue is solved – I reinstalled Arch some time ago, installed ttf-meguri from AUR, and ttf-kanjistrokeorders after that. Things work as expected now; the little numbers only appear on the Kanji Lookup Display.

    Second, right before I reinstalled, I noticed that the Kanji Stroke Orders font was used on some pages in Firefox as well – so it wasn't a gwaei-only bug. I'm terribly sorry for causing such a fuss over nothing! I really didn't notice it until I saw some numbered characters pop up on some Japanese website.

    And last: You will find lots of Japanese TTF fonts in the AUR in case you haven't noticed until now. Have fun with Arch, good luck with development, and thanks for this incredibly useful program.

     
  • runiq

    runiq - 2010-05-31

    Okay, I finally also found out what exactly caused this: It was just that KanjiStrokeOrders was preferred over Meguri in /etc/fonts/conf.avail/65-nonlatin.conf. I put

    <family>Meguri P</family>

    at the top of the three lists in that file (serif, sans-serif, and monospace) and now it gets used where it should. Kanji Stroke Orders is finally only used on the Kanji Lookup Display, as it should.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks