Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upKanjipad is too strict on errors #787
Comments
This comment has been minimized.
This comment has been minimized.
|
That is true - internal Kanjipad uses a rather very simple algorithm which is quite unforgiving on stroke order, and, most importantly, stroke count. There is a possibility to use the KanjiPad Extension which should be way more forgiving: http://aedict.eu/kanjipadextension/index.html |
mvysny
self-assigned this
Aug 9, 2017
mvysny
added
the
user feedback needed
label
Aug 9, 2017
This comment has been minimized.
This comment has been minimized.
|
Yes I was talking about the KanjiPad extension.
It is not as easy to use as a few other apps on iOS like "Shirabe Jisho".
It'd take me minutes just to redraw the kanji again and again in different
stroke orders to get the kanji I want and sometimes I'd just give up and
type in the romanized form of the word itself for the kanji.
That said, I really love the app. It is honestly the best Japanese
Dictionary on Android I've ever used while I do understand it still needs
improvements.
Keep up the good work mate, I hope you'll brush up the Kanji Extension soon
(and the GUI too. It looks a bit quite old with all the Material Design
stuff going nowaday you know).
Cheers!
…On Aug 9, 2017 4:21 PM, "Martin Vysny" ***@***.***> wrote:
That is true - internal Kanjipad uses a rather very simple algorithm which
is quite unforgiving on stroke order, and, most importantly, stroke count.
There is a possibility to use the KanjiPad Extension which should be way
more forgiving: http://aedict.eu/kanjipadextension/index.html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#787 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Adbiuc7PA4Sju1HkDCHVoDmpIggQeBbFks5sWXn-gaJpZM4Oxwbq>
.
|
This comment has been minimized.
This comment has been minimized.
I'm sorry to hear that. Is it possible to learn which algorithm does Shirabe Jisho use? Perhaps it uses some kind of open/free algorithm which could then be integrated into Aedict...
Thanks, and it is indeed true that there's a room for improvement.
True. Unfortunately I am no UX designer and I have no money to hire UX designer... I'd love to have a newest material design, but I need concrete hints as on which part of the app to improve. The problem with Material Design is that:
So, it's not easy to do the design right; the low income from Aedict forbids me to hire an UX guy. From 10 eur I charge, the state will take 20% VAT and Google will take 30% as a fee; Aedict is selling really slowly nowadays so I earn like ~80 eur per month (less than 3 eur per working day). That is nowhere near to sustain me, not even another UX guy. It is a known fact that it's very hard to sell apps on Google Play and actually make a living out of those - only perhaps games earn enough to sustain the dev team. |
This comment has been minimized.
This comment has been minimized.
|
Also see #768. In short, Android API sucks, developing for Android sucks, and the money is laughable. Even paid apps are nothing but a hobby, so it's expected to see mediocre quality. |
This comment has been minimized.
This comment has been minimized.
|
According to its info tab I think it uses KanjiVG by Ulrich Apel? You
should try and take a look at this app if you have an iOS device. It feels
almost perfect to me. But nah I realy hate iOS.
I'm sorry to hear about your financial problem regarding hiring an UX
Designer. I know your Patreon link and I hope some small contribution of
mine can be of use in the future.
…On Aug 9, 2017 4:55 PM, "Martin Vysny" ***@***.***> wrote:
It is not as easy to use as a few other apps on iOS like "Shirabe Jisho".
It'd take me minutes just to redraw the kanji again and again in different
stroke orders to get the kanji I want and sometimes I'd just give up and
type in the romanized form of the word itself for the kanji.
I'm sorry to hear that. Is it possible to learn which algorithm does
Shirabe Jisho use? Perhaps it uses some kind of open/free algorithm which
could then be integrated into Aedict...
That said, I really love the app. It is honestly the best Japanese
Dictionary on Android I've ever used while I do understand it still needs
improvements.
Thanks, and it is indeed true that there's a room for improvement.
the GUI looks a bit quite old with all the Material Design stuff going
nowaday you know
True. Unfortunately I am no UX designer and I have no money to hire UX
designer... I'd love to have a newest material design, but I need concrete
hints as on which part of the app to improve. The problem with Material
Design is that:
- it contains questionable UX guidelines (such as buttons at the top,
basically unreachable with your thumb)
- it wastes a lot of space, which is in conflict with Aedict
philosophy of cramming lots of information onto one screen
So, it's not easy to do the design right; the low income from Aedict
forbids me to hire an UX guy.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#787 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Adbiuc8TeceFmpS1hUel__lZM9ZdZ2T9ks5sWYIbgaJpZM4Oxwbq>
.
|
This comment has been minimized.
This comment has been minimized.
|
Thank you very much for your contribution, it's highly appreciated! I also hope that after the money is raised, I'll be able to pay an UX guy. Actually, the Kanjipad Extension also uses a modified version of KanjiVG, so the results should be at least similar. Hard to say; perhaps Shirabe Jisho modified the engine in a different way, or maybe they do some other tricks? I am trying hard to think of a way on how to have the very same input going into Shirabe and into the Kanjipad, so that I could see the outputs and debug Kanjipad to find the bug, but I can't see any easy way to do so... |
This comment has been minimized.
This comment has been minimized.
|
Also the +-2 strokes option auto-turns off after 10 strokes since then the algorithm starts to get really slow. But perhaps Shirabe doesn't do that? Does Shirabe return e.g. 12-stroked kanjis even when 13 strokes are drawn? |
This comment has been minimized.
This comment has been minimized.
|
On Wed, Aug 9, 2017 at 5:21 PM Martin Vysny ***@***.***> wrote:
Also the +-2 strokes option auto-turns off after 10 strokes since then the
algorithm starts to get really slow. But perhaps Shirabe doesn't do that?
Does Shirabe return e.g. 12-stroked kanjis even when 13 strokes are drawn?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#787 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AdbiueexQcXH2fkrBmu_AliJcRaOi0Rfks5sWYgegaJpZM4Oxwbq>
.
I'm sorry to say this but I'm not really a developer myself these days so I
don't really have a good idea on how Shirabe works here. I think you should
go and give it a try yourself. Try to draw a sophisticated Kanji on both
apps like a JLPT N5 guy struggling with "線", maybe you'll have it figured
out. From my point of view sometimes when I skip strokes (like adding 2
different stroke in 1 stroke it'd come out naturally the kanji I want). On
Aedict I do have to be really careful about the number of strokes though.
|
This comment has been minimized.
This comment has been minimized.
|
In my eyes that implies that Shirabe is quite forgiving on stroke count even on more complex kanjis and thus uses the |
mvysny
added
bug
and removed
user feedback needed
labels
Aug 9, 2017
This comment has been minimized.
This comment has been minimized.
|
On Wed, Aug 9, 2017 at 5:36 PM Martin Vysny ***@***.***> wrote:
In my eyes that implies that Shirabe is quite forgiving on stroke count
even on more complex kanjis and thus uses the +-2 strokes even for
complex kanjis. I will thus make Aedict to honor the +-2 strokes setting
for a complex kanjis as well; after the next Aedict 3.42 is released, let
us observe whether the situation improves or not.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#787 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AdbiuQNp8CYTioAyBeZFfBZiW07DQCCoks5sWYu2gaJpZM4Oxwbq>
.
Looking forward to it. I'll give you some feedback afterwards. Keep up the
good work mate.
|
This comment has been minimized.
This comment has been minimized.
|
Thanks! Fixed in 3.42. To my horror, I realized that the +-2 strokes checkbox was completely ignored in 3.41, so it should work properly now. |
mvysny
closed this
Sep 12, 2017
This comment has been minimized.
This comment has been minimized.
|
On Tue, Sep 12, 2017 at 6:18 PM Martin Vysny ***@***.***> wrote:
Thanks! Fixed in 3.42. To my horror, I realized that the +-2 strokes
checkbox was completely ignored in 3.41, so it should work properly now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#787 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AdbiuQjVPDNr2vnHVPKOuGB5iKYYcfHJks5shmiYgaJpZM4Oxwbq>
.
Nice hearing from you again. I'll test it out for a couple of days. Thanks
for you hard work as always mate!
|
This comment has been minimized.
This comment has been minimized.
|
Actually you will need to wait until 3.42 is out; it's not yet out since I want to fix several more bugs ;) |
This comment has been minimized.
This comment has been minimized.
|
On Tue, Sep 12, 2017 at 6:37 PM Martin Vysny ***@***.***> wrote:
Actually you will need to wait until 3.42 is out; it's not yet out since I
want to fix several more bugs ;)
Also, +-2 strokes is very slow for kanjis with 12 and more strokes, thus
only kanjis with +-1 stroke will be searched for kanjis with 12 or more
strokes even though "+-2 strokes" checkbox is checked. Let's check whether
this is enough for more accurate results or whether I really need to
perform a full +-2 strokes search.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#787 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AdbiudB-x3C_b9v8Gvf1afkQqre7DaSuks5shmzjgaJpZM4Oxwbq>
.
Have you tried to compare it with Shirabe Jisho's Kanji engine?
|
This comment has been minimized.
This comment has been minimized.
|
Kanjipad really is better after the update. I'll give you some more
feedback after a while if there is any problem.
Thanks for your hard work.
2017/09/12 午後6:39 "Ngô Trường Minh Đức" <nanayakuro@gmail.com>:
On Tue, Sep 12, 2017 at 6:37 PM Martin Vysny ***@***.***> wrote:
Actually you will need to wait until 3.42 is out; it's not yet out since I
want to fix several more bugs ;)
Also, +-2 strokes is very slow for kanjis with 12 and more strokes, thus
only kanjis with +-1 stroke will be searched for kanjis with 12 or more
strokes even though "+-2 strokes" checkbox is checked. Let's check whether
this is enough for more accurate results or whether I really need to
perform a full +-2 strokes search.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#787 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AdbiudB-x3C_b9v8Gvf1afkQqre7DaSuks5shmzjgaJpZM4Oxwbq>
.
Have you tried to compare it with Shirabe Jisho's Kanji engine?
|
Akinori0713 commentedAug 9, 2017
Thank you for making the time to report a bug and make Aedict better!
Thank you for your interest in Aedict. Prior submitting bugs, please make sure that you have newest Aedict from Google Play, Blackberry store or Amazon App store.
A screenshot is often worth a thousand words, so please make sure to include one ;)
Income from Google Play and other stores is rather small, and is made even smaller by the 30% fee charged by Google and 20% VAT charged in most countries. Please consider supporting the project on Patreon:
https://www.patreon.com/bePatron?u=2914375