GlyphWiki logo
導航
幫助
搜索
工具箱
其他語言
用戶頁面討論編輯歷史

用戶-對話:aparthum

字形維基(GlyphWiki), 自由的字形數據庫

  • 翻訳していただき、ありがとうございます。--kamichi 2009年3月15日(日) 23:23
    • いいえ、どういたしまして。私はアメリカ人ので、日本語で書くのが難しいんです。でも、ちょっと読むことができますから、翻訳を助けようとします。 -aparthum 08:28, 16 March 2009

  • Thanks for helping out. My translations are far from fluent, so the effort is appreciated. How did you find out about this project? jeroen 19:20, 20 March 2009
    • Your English is good enough for the most part, but yeah, it is a lot of work when you have to decide the right way to say something in a language that is not your most comfortable one. I’ve been there all too often.
      • Blame my Dutch nationality. :) jeroen 2009年3月22日(日) 06:25
      • Indeed! I curse your centuries of history as a widespread trading nation, your educational system’s foreign language programs, and your language’s linguistic proximity! Bah! :< -aparthum 03:46, 25 March 2009
    • I found this project because I am an amateur translator (and a mediocre programmer), and while I’m not an impatient person, I don’t like the fact that practically all electronic dictionaries use very slow lookup methods: you get to enter a limited number of parameters and then you have to look, and that’s assuming you get everything right on the first shot (alternatively, you could just use some IME or other, but that means you already know the thing you want to look up!). If looking up a dictionary entry is taking more than 30 seconds, there is some sort of methodology flaw... and it’s taking more than 30 seconds. So my goal is to build a cross-platform dictionary program that can address radical, SKIP code, and four-corner code lookup, etc. simultaneously (instead of separately) and intuitively. That way, I can stop wasting time looking up some obscure kanji (and forgetting the rest of the sentence I was translating in the process).
      • Exactly. This is why I am developing a dictionary interface that will let users use what they see and recognise. The methods you mention are good, but I want to take it one step further and make the structure of kanji accessible to the user. If you see the word 躊躇 written somewhere, and copy and paste is not an option, than you should be able to say “Give me all 2 kanji compound words that have 足 on the left of both kanji” to the software and be done with it. For this I need to be able to draw kanji (GlyphWiki) and need to know about its composition (CHISE and derivatives). jeroen 2009年3月22日(日) 06:25
      • That sounds a bit more ambitious than what I’m messing around with, but I suppose my programming talents lie more in taking good UI paradigms and turning them into horrendous failures! -aparthum 03:46, 25 March 2009
    • Fortunately, Jim Breen’s KANJIDIC2 provides all the database information I could ever need. Unfortunately, I want this application to be mostly self-contained and cross-platform, and there is definitely a lack of kanji fonts that come with sufficient numbers of kanji, look okay (without totally mangling the characters, either), and come with a minimum of legal monkey business attached. So even settling for Hanazono without mucking around a whole lot with KAGE, GlyphWiki has more than a few things going for me :) -aparthum 05:25, 22 March 2009
      • Have a look at the Unicode Unihan database too: http://www.unicode.org/reports/tr38/ . jeroen 2009年3月22日(日) 06:25
      • You may find gwdrawfonttool interesting. It is still very much in an alpha state, but have a look if you would like too: http://gwdrawfonttool.sourceforge.net/ . By using Python and GTK+/Cairo the software remains cross platform too. jeroen 2009年3月22日(日) 06:25
      • I plan on using it at some point. I use a Mac, which will make things “interesting” to say the least (GTK+ support on Mac is bad because Mac X11 support is not really what it could be... you could also blame the fact that GTK+ thinking placed on top of Cocoa thinking leads to iffy behavior). -aparthum 03:46, 25 March 2009

  • I've merged GlyphWiki:GlyphNaming and GlyphWiki:GivingAGlyphItsName; you accidentally started a new article. There is currently no easy way to tell if a Japanese page has a translated equivalent, so that is bound to happen from time to time. :( jeroen 20:27, 20 March 2009
    • Yeah, that’s the problem when you don’t have all the whiz-bang-doodle category and reverse-search features of Mediawiki and other super-capable resource-gobbling wiki software. But in the end, it’s doesn’t add up to all that many pages, so I don’t mind.... -aparthum 05:25, 22 March 2009