Re: Ankidroid Hebrew deck that looks great!
788 views
Skip to first unread message
iniju
Jul 8, 2012, 7:12:32 PM7/8/12
to anki-a...@googlegroups.com
Thank you for this update.
I should mention here that this font is not mapping to Unicode, but to Latin alphabet.
On Friday, 15 June 2012 19:08:10 UTC+1, Francis wrote:
Meaning that if I try to render a piece of Hebrew I copied from wikipedia with this font, it will just render as Arial, or whatever the default font is.
To see Hebrew on this font, I would have to enter a normally latin looking text like "abc", which this font maps to hebrew characters over a certain mapping.
Cheers
Kostas
On Friday, 15 June 2012 19:08:10 UTC+1, Francis wrote:
After much seeking, I have found one deck that works great for biblical Hebrew: "Hebrew OT vocab (bwhebb font)". It requires the installation of the bwhebb font (copy to the Ankidroid/fonts/ folder and create the fonts folder if there is none). The font is free from the Bibleworks site. The pointing looks perfect!
iniju
Jul 11, 2012, 11:22:31 AM7/11/12
to anki-a...@googlegroups.com
On the other hand, this provides an alternative way to fix the problem:
By mapping the Unicode characters to latin and forcing use of this font! This mapping will be done on the fly, just within webview.
The only hurdle is that the font should be downloaded by the user and installed in the AnkiDroid/fonts directory. I don't think we can bundle it with AnkiDroid because of licencing (and it's better to not fatten up the apk anymore).
Kostas
Dennis Meulensteen
Jul 11, 2012, 1:08:13 PM7/11/12
to anki-a...@googlegroups.com
I have all the mapping stuff already working for the Cardo font. Currently it is a simple piece of code. Problem is that there are still certain combinations of letters and marks that render poorly using Cardo in Android.
I would like to evaluate the bwhebb font and compare it to how Cardo renders. I do expect that the translation would be more complex because a combination of Unicode chars would often be needed to render one bwhebb glyph, but not always...
If the licence terms permit it may be a decent way of getting classical Hebrew to render properly.
The download algorithm is a bit of a challenge though. If anyone can point me to the right place in Ankidroid where downloads are handled I'd be grateful.
Progress has been slow because I don't have a lot of free time between work, family and my studies.
Dennis.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
You received this message because you are subscribed to the Google Groups "AnkiDroid" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/anki-android/-/662t0Ab0-PUJ.
To post to this group, send an email to anki-a...@googlegroups.com.
To unsubscribe from this group, send email to anki-android...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/anki-android?hl=en-GB.
I would like to evaluate the bwhebb font and compare it to how Cardo renders. I do expect that the translation would be more complex because a combination of Unicode chars would often be needed to render one bwhebb glyph, but not always...
If the licence terms permit it may be a decent way of getting classical Hebrew to render properly.
The download algorithm is a bit of a challenge though. If anyone can point me to the right place in Ankidroid where downloads are handled I'd be grateful.
Progress has been slow because I don't have a lot of free time between work, family and my studies.
Dennis.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
You received this message because you are subscribed to the Google Groups "AnkiDroid" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/anki-android/-/662t0Ab0-PUJ.
To post to this group, send an email to anki-a...@googlegroups.com.
To unsubscribe from this group, send email to anki-android...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/anki-android?hl=en-GB.
iniju
Jul 11, 2012, 2:05:02 PM7/11/12
to anki-a...@googlegroups.com
Hi Dennis,
I think we can make the fix for now without worrying about the downloading for two reasons:
1. I'm not sure if we can include a "clear attribution to Bibleworks" as the licencing of the font expects within AnkiDroid just in order to circumvent an Android bug. I'm not the expert on AnkiDroid licencing.
2. I would like to move all these hackish solutions and workarounds to plugins in the near future. A separate plugin can include a downloader if required, but it's a bit of bloat to put that into AnkiDroid proper, since most users don't need this.
For now, we can popup a dialog when the user activates the Hebrew-Fix preference that explains how and where to find the required font.
I don't know how familiar you are with the AnkiDroid code (please only consider 2.0 version, the master branch in github), but the mapping should go into com.ichi2.libanki.hooks.HebrewFix.java in the method applyHebrewFix.
I don't know how familiar you are with the AnkiDroid code (please only consider 2.0 version, the master branch in github), but the mapping should go into com.ichi2.libanki.hooks.HebrewFix.java in the method applyHebrewFix.
If you need any help/advice on the coding part, please ask.
If on the other hand you don't have time, I'll try to do it myself, but I have practically zero knowledge on Hebrew language and Unicode RTL and I'm not going to use the fix myself, so any advice and feedback is greatly appreciated and will lead to a better solution.
You also mention that you have already done something similar for Cardo. How? Cardo doesn't render the vowels properly as far as I know.
Cheers,
Kostas
To unsubscribe from this group, send email to anki-android+unsubscribe@googlegroups.com.
Dennis Meulensteen
Jul 11, 2012, 2:54:17 PM7/11/12
to anki-a...@googlegroups.com
Re; 1. Cardo is FOSS so licencing is not an issue.
2; OK, sounds good to me.
Code familiarity; I've not looked at 2.0 but the method name sure sounds familiar! Not a problem. After I get back from our little holiday I'll implement it right away.
Cardo rendering; most vowels and such are fine, using my code, with some notable exceptions. I'll try to fix these with my font editor but I still have not found the root cause. Once I have that it will be trivial to fix any remaining rendering issues.
Mapping the font and providing the fix for 2.0 is something I can handle. It was coding a download manager that was a bit over the top.
Give me a couple more weeks and you will have the code. It may take longer to tweak the font to 100% though.
Dennis
2; OK, sounds good to me.
Code familiarity; I've not looked at 2.0 but the method name sure sounds familiar! Not a problem. After I get back from our little holiday I'll implement it right away.
Cardo rendering; most vowels and such are fine, using my code, with some notable exceptions. I'll try to fix these with my font editor but I still have not found the root cause. Once I have that it will be trivial to fix any remaining rendering issues.
Mapping the font and providing the fix for 2.0 is something I can handle. It was coding a download manager that was a bit over the top.
Give me a couple more weeks and you will have the code. It may take longer to tweak the font to 100% though.
Dennis
iniju <inigo....@gmail.com> wrote:
To view this discussion on the web, visit https://groups.google.com/d/msg/anki-android/-/W9duT0HMFQYJ.
To post to this group, send an email to anki-a...@googlegroups.com.
To unsubscribe from this group, send email to anki-android...@googlegroups.com.
Dotan Cohen
Jul 11, 2012, 3:16:37 PM7/11/12
to anki-a...@googlegroups.com
On Wed, Jul 11, 2012 at 6:22 PM, iniju <inigo....@gmail.com> wrote:
> On the other hand, this provides an alternative way to fix the problem:
>
> By mapping the Unicode characters to latin and forcing use of this font!
> This mapping will be done on the fly, just within webview.
> The only hurdle is that the font should be downloaded by the user and
> installed in the AnkiDroid/fonts directory. I don't think we can bundle it
> with AnkiDroid because of licencing (and it's better to not fatten up the
> apk anymore).
>
That is not a solution, and it is hardly a workaround. The real
> On the other hand, this provides an alternative way to fix the problem:
>
> By mapping the Unicode characters to latin and forcing use of this font!
> This mapping will be done on the fly, just within webview.
> The only hurdle is that the font should be downloaded by the user and
> installed in the AnkiDroid/fonts directory. I don't think we can bundle it
> with AnkiDroid because of licencing (and it's better to not fatten up the
> apk anymore).
>
solution would be to fix the Hebrew support.
I had opportunity to use AnkiDroid for a few weeks in April, and all
my decks are in Hebrew as that is my native language. I didn't have
much trouble, everything "just worked". Numbers were displayed
backwards, though, which is something that I've never seen in any
environment.
I don't recall if vowel points worked correctly or not. If so then I
would have mentioned it, I did mention my experiences here on the
list.
--
Dotan Cohen
http://gibberish.co.il
http://what-is-what.com
Dotan Cohen
Jul 11, 2012, 3:18:36 PM7/11/12
to anki-a...@googlegroups.com
On Wed, Jul 11, 2012 at 9:05 PM, iniju <inigo....@gmail.com> wrote:
> Hi Dennis,
>
> I think we can make the fix for now without worrying about the downloading
> for two reasons:
> 1. I'm not sure if we can include a "clear attribution to Bibleworks" as the
> licencing of the font expects within AnkiDroid just in order to circumvent
> an Android bug. I'm not the expert on AnkiDroid licencing.
> 2. I would like to move all these hackish solutions and workarounds to
> plugins in the near future. A separate plugin can include a downloader if
> required, but it's a bit of bloat to put that into AnkiDroid proper, since
> most users don't need this.
>
> For now, we can popup a dialog when the user activates the Hebrew-Fix
> preference that explains how and where to find the required font.
>
> I don't know how familiar you are with the AnkiDroid code (please only
> consider 2.0 version, the master branch in github), but the mapping should
> go into com.ichi2.libanki.hooks.HebrewFix.java in the method applyHebrewFix.
> If you need any help/advice on the coding part, please ask.
>
> If on the other hand you don't have time, I'll try to do it myself, but I
> have practically zero knowledge on Hebrew language and Unicode RTL and I'm
> not going to use the fix myself, so any advice and feedback is greatly
> appreciated and will lead to a better solution.
>
> You also mention that you have already done something similar for Cardo.
> How? Cardo doesn't render the vowels properly as far as I know.
>
I don't have an Android device at the moment, but if I can help in any
> Hi Dennis,
>
> I think we can make the fix for now without worrying about the downloading
> for two reasons:
> 1. I'm not sure if we can include a "clear attribution to Bibleworks" as the
> licencing of the font expects within AnkiDroid just in order to circumvent
> an Android bug. I'm not the expert on AnkiDroid licencing.
> 2. I would like to move all these hackish solutions and workarounds to
> plugins in the near future. A separate plugin can include a downloader if
> required, but it's a bit of bloat to put that into AnkiDroid proper, since
> most users don't need this.
>
> For now, we can popup a dialog when the user activates the Hebrew-Fix
> preference that explains how and where to find the required font.
>
> I don't know how familiar you are with the AnkiDroid code (please only
> consider 2.0 version, the master branch in github), but the mapping should
> go into com.ichi2.libanki.hooks.HebrewFix.java in the method applyHebrewFix.
> If you need any help/advice on the coding part, please ask.
>
> If on the other hand you don't have time, I'll try to do it myself, but I
> have practically zero knowledge on Hebrew language and Unicode RTL and I'm
> not going to use the fix myself, so any advice and feedback is greatly
> appreciated and will lead to a better solution.
>
> You also mention that you have already done something similar for Cardo.
> How? Cardo doesn't render the vowels properly as far as I know.
>
way I would be happy to. I have quite a bit of experience with Hebrew
and how it is supposed to render!
Flavio Lerda
Jul 11, 2012, 3:48:28 PM7/11/12
to anki-a...@googlegroups.com
Dotan:
--
Flavio Lerda
It might be possible for you to help with verifying what is rendered correctly or incorrectly using the emulator.
It is available for Windows/Linux/Mac and it is pretty close to the actual device in terms of experience.
I am not particularly working on Hebrew support, but I would be happy to help if you need assistance setting up the emulator for testing.
-Flavio
--
You received this message because you are subscribed to the Google Groups "AnkiDroid" group.
To post to this group, send an email to anki-a...@googlegroups.com.
To unsubscribe from this group, send email to anki-android...@googlegroups.com.
Flavio Lerda
Dotan Cohen
Jul 11, 2012, 4:18:46 PM7/11/12
to anki-a...@googlegroups.com
On Wed, Jul 11, 2012 at 10:48 PM, Flavio Lerda <fle...@gmail.com> wrote:
> Dotan:
>
> It might be possible for you to help with verifying what is rendered
> correctly or incorrectly using the emulator.
> It is available for Windows/Linux/Mac and it is pretty close to the actual
> device in terms of experience.
>
> I am not particularly working on Hebrew support, but I would be happy to
> help if you need assistance setting up the emulator for testing.
>
> -Flavio
>
Thanks. I am downloading the SDK here to get the emulator:
> Dotan:
>
> It might be possible for you to help with verifying what is rendered
> correctly or incorrectly using the emulator.
> It is available for Windows/Linux/Mac and it is pretty close to the actual
> device in terms of experience.
>
> I am not particularly working on Hebrew support, but I would be happy to
> help if you need assistance setting up the emulator for testing.
>
> -Flavio
>
http://developer.android.com/sdk/index.html
Once I have it installed, should I build Ankidroid from source? I see
a bunch of apk files here, but no source code:
http://code.google.com/p/ankidroid/downloads/list
Flavio Lerda
Jul 11, 2012, 4:56:11 PM7/11/12
to anki-a...@googlegroups.com
Hello Dotan:
--
Flavio Lerda
The source code is in github.
Note: you will need to install the emulator images for a specific version of Android.
Looking at:
I would suggest checking Gingerbread (API 9) as a starting point.
Overall it is used to make sure that things work well on different versions.
Someone familiar with Hebrew support knows which version would be most appropriate?
After that, you probably can install the latest 2.0 alpha on the downloads list to get started.
-Flavio
--
You received this message because you are subscribed to the Google Groups "AnkiDroid" group.
To post to this group, send an email to anki-a...@googlegroups.com.
To unsubscribe from this group, send email to anki-android...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/anki-android?hl=en-GB.
Flavio Lerda
iniju
Jul 12, 2012, 5:37:59 AM7/12/12
to anki-a...@googlegroups.com
Hi Dotan,
Maybe this thread is not clear. Just so that we are all on the same page regarding the nature of the problem and the necessity for a workaround, here's some background:
We're only referring to text with Hebrew vowels here, which is necessary for users studying biblical Hebrew.
Modern Hebrew looks fine and doesn't need any fix or workaround.
As far as I know we have spent a lot of time and effort trying to get Hebrew vowels to render correctly in AnkiDroid, without success. Here is the last thread on that issue: https://groups.google.com/forum/?fromgroups#!searchin/anki-android/hebrew/anki-android/kHabdJuAElc/znFokguz5M4J
The problem is a bug in of Android OS. Here is the Android bug report: http://code.google.com/p/android/issues/detail?id=14661
Since this is an Android bug, we can only provide a workaround or somehow convince Google to fix it and backport the fix to old APIs.
To see the problem with an emulator, just try to visit a webpage that has Biblical Hebrew, using the stock android browser. Here is a test page kindly setup by Robert Siemer, when we last revisited this problem: http://backsla.sh/bidi-forced-rtl
Any ideas for a fix are welcome:
- Text remapping prior to rendering and use of a modified font (personal favourite and current topic of this thread).
- Modifying the text before rendering without touching the font (this has been tried with no success, but feel free to try).
- Auto-rendering hebrew as images (I haven't found a text-to-image library or webservice that can render hebrew vowels).
- Javascript/CSS solutions (haven't tried that yet).
Cheers,
Kostas
iniju
Jul 12, 2012, 5:52:04 AM7/12/12
to anki-a...@googlegroups.com
Dennis,
Thanks for this. Please let me know if you need any help with it.
I can make the downloader in the meantime.
Kostas
Dotan Cohen
Jul 15, 2012, 8:11:52 AM7/15/12
to anki-a...@googlegroups.com
Just an update, I am having a very hard time with Ubuntu, I seem to be
hitting this bug:
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/852101?comments=all
Seeing how I cannot open Skype or GoogleEarth I see that this is the
problem! When I get it sorted out I'll get on this.
hitting this bug:
https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/852101?comments=all
Seeing how I cannot open Skype or GoogleEarth I see that this is the
problem! When I get it sorted out I'll get on this.
Dotan Cohen
Jul 15, 2012, 8:49:52 AM7/15/12
to anki-a...@googlegroups.com
On Thu, Jul 12, 2012 at 12:37 PM, iniju <inigo....@gmail.com> wrote:
> The problem is a bug in of Android OS. Here is the Android bug report:
> http://code.google.com/p/android/issues/detail?id=14661
> Since this is an Android bug, we can only provide a workaround or somehow
> convince Google to fix it and backport the fix to old APIs.
>
Thanks. You will see that I have commented on that bug, as I have had
> The problem is a bug in of Android OS. Here is the Android bug report:
> http://code.google.com/p/android/issues/detail?id=14661
> Since this is an Android bug, we can only provide a workaround or somehow
> convince Google to fix it and backport the fix to old APIs.
>
other people test it for me. I posted in their name.
DennisMe
Jul 25, 2012, 5:39:10 AM7/25/12
to anki-a...@googlegroups.com
Hi all,
I finally ported my modifications to AnkiDroid 2 and it tests out fine!
Alas, the work is based on the zip download as I have spent way more time getting eclipse and git to play nice together than I consider worthwile. So I have now given that up for good.
The good news: Due to the nice hooks structure in 2.0 it all fits in one file! (not counting the required font, that is).
I have also looked at the bwhebb font that Dotan so kindly reminded me of (I was hoping to be able to forget that carp in the age of unicode...) The trick they use is quite dirty when it comes to human use, but perfectly suited to machine translation, so I will be adding that to my solution at a later date. It boils down to dividing the consonants into two (or more) groups of "Wide" and "Small" characters. Vowels (theoretically all nikudot) are added twice, one for pairing with a wide consonant and another for pairing with a small consonant. When a vowel is detected there will be a check if it needs to be replaced by a small one in stead of the wide one (default) This should fix 99% of the remaining few alignment issues. Using Bwhebb is not ideal due to licencing but also the approach would yield some nasty illegible code IMHO (yes, I'm implying my code IS legible BTW!).
For now the Tohu font only includes wide vowels. This works well enough in most cases. Anyone who comes across any errors is welcome to mail me or post here and I'll code the required exceptions into my font and translation table.
The reason all this BS is needed is because ANDROID doesn't handle (pointed) hebrew MIXED with western scripts properly. Modern Hebrew is not that bad at all but things really screw up when you mix western LTR and Hebrew RTL. Even using a very elaborate scholarly font like Cardo (on which Tohu is based) does not solve the basic issues because Android also has EXTREMELY limited support for kerning (gpos look up tables etc). Obviously it would be best if this were fixed by the Android devs, but they haven't been in any hurry up to now. Besides it would then have to be back-ported for older devices (like my hacked e-reader or older phone) and I don't see that happening any time soon.
It would be great is someone could put my edited file into the source so we cal all benefit.
Thanks,
Dennis
I finally ported my modifications to AnkiDroid 2 and it tests out fine!
Alas, the work is based on the zip download as I have spent way more time getting eclipse and git to play nice together than I consider worthwile. So I have now given that up for good.
The good news: Due to the nice hooks structure in 2.0 it all fits in one file! (not counting the required font, that is).
I have also looked at the bwhebb font that Dotan so kindly reminded me of (I was hoping to be able to forget that carp in the age of unicode...) The trick they use is quite dirty when it comes to human use, but perfectly suited to machine translation, so I will be adding that to my solution at a later date. It boils down to dividing the consonants into two (or more) groups of "Wide" and "Small" characters. Vowels (theoretically all nikudot) are added twice, one for pairing with a wide consonant and another for pairing with a small consonant. When a vowel is detected there will be a check if it needs to be replaced by a small one in stead of the wide one (default) This should fix 99% of the remaining few alignment issues. Using Bwhebb is not ideal due to licencing but also the approach would yield some nasty illegible code IMHO (yes, I'm implying my code IS legible BTW!).
For now the Tohu font only includes wide vowels. This works well enough in most cases. Anyone who comes across any errors is welcome to mail me or post here and I'll code the required exceptions into my font and translation table.
The reason all this BS is needed is because ANDROID doesn't handle (pointed) hebrew MIXED with western scripts properly. Modern Hebrew is not that bad at all but things really screw up when you mix western LTR and Hebrew RTL. Even using a very elaborate scholarly font like Cardo (on which Tohu is based) does not solve the basic issues because Android also has EXTREMELY limited support for kerning (gpos look up tables etc). Obviously it would be best if this were fixed by the Android devs, but they haven't been in any hurry up to now. Besides it would then have to be back-ported for older devices (like my hacked e-reader or older phone) and I don't see that happening any time soon.
It would be great is someone could put my edited file into the source so we cal all benefit.
Thanks,
Dennis
iniju
Jul 25, 2012, 11:14:16 AM7/25/12
to anki-a...@googlegroups.com
Woohoo!
This is great news! I'll start integrating your code to the tree tonight.
I understand your frustration with the status of RTL support by Android.
Regarding the downloader, is it possible to include your modified font to the Downloads page of the issue tracker, so that the downloader (when it is ready) can target a fixed location that can hard-coded? Otherwise what other location would work?
Cheers,
Kostas
Dennis Meulensteen
Jul 25, 2012, 2:08:41 PM7/25/12
to anki-a...@googlegroups.com
Thanks IniJu,
It doesn't matter to me where the font is kept. Just bear in mind I will need to provide updates from time to time. In practice I expect this won't happen too often though.
Dennis.
--
Sent from my hacked e-reader please excuse my brevity.
It doesn't matter to me where the font is kept. Just bear in mind I will need to provide updates from time to time. In practice I expect this won't happen too often though.
Dennis.
--
Sent from my hacked e-reader please excuse my brevity.
iniju <inigo....@gmail.com> wrote:
It would be g reat is someone could put my edited file into the source so we cal all benefit.
Thanks,
Dennis
--
You received this message because you are subscribed to the Google Groups "AnkiDroid" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/anki-android/-/ctUcDUqISywJ.
To post to this group, send an email to anki-a...@googlegroups.com.
To unsubscribe from this group, send email to anki-android...@googlegroups.com.
Dotan Cohen
Jul 25, 2012, 2:35:44 PM7/25/12
to anki-a...@googlegroups.com
On Wed, Jul 25, 2012 at 12:39 PM, DennisMe <den...@meulensteen.nl> wrote:
> The reason all this BS is needed is because ANDROID doesn't handle (pointed)
> hebrew MIXED with western scripts properly. Modern Hebrew is not that bad at
> all but things really screw up when you mix western LTR and Hebrew RTL. Even
> using a very elaborate scholarly font like Cardo (on which Tohu is based)
> does not solve the basic issues because Android also has EXTREMELY limited
> support for kerning (gpos look up tables etc). Obviously it would be best if
> this were fixed by the Android devs, but they haven't been in any hurry up
> to now. Besides it would then have to be back-ported for older devices (like
> my hacked e-reader or older phone) and I don't see that happening any time
> soon.
>
I've given up with the emulator on *buntu, but I could get some folks
> The reason all this BS is needed is because ANDROID doesn't handle (pointed)
> hebrew MIXED with western scripts properly. Modern Hebrew is not that bad at
> all but things really screw up when you mix western LTR and Hebrew RTL. Even
> using a very elaborate scholarly font like Cardo (on which Tohu is based)
> does not solve the basic issues because Android also has EXTREMELY limited
> support for kerning (gpos look up tables etc). Obviously it would be best if
> this were fixed by the Android devs, but they haven't been in any hurry up
> to now. Besides it would then have to be back-ported for older devices (like
> my hacked e-reader or older phone) and I don't see that happening any time
> soon.
>
on the Israeli Linux LUG list to test. This is the first mention that
I see of the problem being attributed to mixed RTL (dotted) and LTR
text. Tell me, would a mixed webpage demonstrate the issue on the
stock Android browser? For instance, would the following text in a
webpage, if displayed correctly, mean that the issue is resolved on
the device in question:
My name is דוֹתַן כֹהֵן in Hebrew.
שמִי Dotan Cohen בּאָנגלִית.
If so then I will simply put that text on a webpage and send users to
check how it displays. Israeli users show that the linked bug is in
fact resolved on Israeli Android devices.
Nicolas Raoul
Jul 25, 2012, 9:16:11 PM7/25/12
to anki-a...@googlegroups.com
Hi all,
Dennis, thank you very much for your work!
Just a reminder for everyone: AnkiDroid is in beta phase, which means
that code is "frozen", no additional feature is merged. We are
supposed to only fix crashes, deck corruptions, and other
life-threatening problems. So font issues might slip to 2.1 ... anyway
it will come very soon after 2.0 I expect :-)
Of course, everyone is still encouraged to write patches, but we might
not merge them immediately.
Thanks for your understanding!
Nicolas Raoul
Dennis, thank you very much for your work!
Just a reminder for everyone: AnkiDroid is in beta phase, which means
that code is "frozen", no additional feature is merged. We are
supposed to only fix crashes, deck corruptions, and other
life-threatening problems. So font issues might slip to 2.1 ... anyway
it will come very soon after 2.0 I expect :-)
Of course, everyone is still encouraged to write patches, but we might
not merge them immediately.
Thanks for your understanding!
Nicolas Raoul
> --
> You received this message because you are subscribed to the Google Groups "AnkiDroid" group.
> You received this message because you are subscribed to the Google Groups "AnkiDroid" group.
DennisMe
Jul 26, 2012, 5:01:17 AM7/26/12
to anki-a...@googlegroups.com
No problem Nicholas,
as long as the work is not wasted I'm not at all bothered. Besides, I have a working version on my phone / e-reader and that is pretty cool in itself ;-)
Once this is released I'll spread the word around the Uni and hopefully some of the profs will jump on this as they have been using out of date solutions for ages up to now.
Dennis
as long as the work is not wasted I'm not at all bothered. Besides, I have a working version on my phone / e-reader and that is pretty cool in itself ;-)
Once this is released I'll spread the word around the Uni and hopefully some of the profs will jump on this as they have been using out of date solutions for ages up to now.
Dennis
> To unsubscribe from this group, send email to anki-android+unsubscribe@googlegroups.com.
DennisMe
Jul 26, 2012, 5:10:00 AM7/26/12
to anki-a...@googlegroups.com
Dotan,
I just browsed to your post (Android.2.1) and indeed, your name is shown backwards in Hebrew.
Also the second "in English" sentence is reversed.
On a cyanogenmod 7 device both actually look reasonable but I have no idea what sort of mods the CM team have introduced.
Dennis
I just browsed to your post (Android.2.1) and indeed, your name is shown backwards in Hebrew.
Also the second "in English" sentence is reversed.
On a cyanogenmod 7 device both actually look reasonable but I have no idea what sort of mods the CM team have introduced.
Dennis
Dotan Cohen
Jul 26, 2012, 5:29:32 AM7/26/12
to anki-a...@googlegroups.com
On Thu, Jul 26, 2012 at 12:10 PM, DennisMe <den...@meulensteen.nl> wrote:
> Dotan,
> I just browsed to your post (Android.2.1) and indeed, your name is shown
> backwards in Hebrew.
> Also the second "in English" sentence is reversed.
> On a cyanogenmod 7 device both actually look reasonable but I have no idea
> what sort of mods the CM team have introduced.
>
> Dennis
>
Thank you. The second line is actually expected to be backwards as I
> Dotan,
> I just browsed to your post (Android.2.1) and indeed, your name is shown
> backwards in Hebrew.
> Also the second "in English" sentence is reversed.
> On a cyanogenmod 7 device both actually look reasonable but I have no idea
> what sort of mods the CM team have introduced.
>
> Dennis
>
did not put an RLE character at the beginning. I would like to see a
screenshot / photo of the display, though, if possible. I'll have
others on the Israeli LUG list do the same.
Thanks.
iniju
Jul 26, 2012, 6:03:01 AM7/26/12
to anki-a...@googlegroups.com
Hi Nicolas,
I think merging this one will be easy as it is concentrated in a single file that can be cut off of the app from the preferences, so it's low risk change. It is not really a new feature, but a bug fix, as it fixes the broken Hebrew support.
Of course it doesn't fix a crash or db corruption problem, so if you don't want to make this exception, I'm ok leaving it for 2.1.
So maybe if we fix the crashes first, we can sneak this in?
Even so, I agree the downloader is beyond scope for 2.0, so if we add it in 2.0 I suggest we just add a popup when this preference (will be off by default) is activated to advise the user on where to download the font.
Kostas
> To unsubscribe from this group, send email to anki-android+unsubscribe@googlegroups.com.
Nicolas Raoul
Jul 26, 2012, 6:06:57 AM7/26/12
to anki-a...@googlegroups.com
Hi Kostas,
Sure feel free :-) You've been very active on this issue (and the rest
of the code!) so you can evaluate the amount of risk better than me.
Cheers!
Nicolas Raoul
>> > anki-android...@googlegroups.com.
Sure feel free :-) You've been very active on this issue (and the rest
of the code!) so you can evaluate the amount of risk better than me.
Cheers!
Nicolas Raoul
>> > For more options, visit this group at
>> > http://groups.google.com/group/anki-android?hl=en-GB.
>> >
>
>> > http://groups.google.com/group/anki-android?hl=en-GB.
>> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "AnkiDroid" group.
> You received this message because you are subscribed to the Google Groups
> "AnkiDroid" group.
> To view this discussion on the web, visit
> https://groups.google.com/d/msg/anki-android/-/lZiNn7gYO8UJ.
>
> To post to this group, send an email to anki-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> anki-android...@googlegroups.com.
> To post to this group, send an email to anki-a...@googlegroups.com.
> To unsubscribe from this group, send email to
iniju
Jul 29, 2012, 5:51:01 PM7/29/12
to anki-a...@googlegroups.com
Should be available in beta11. Modified a bit the logic to leave parentheses rational and numerals in LTR.
Thanks for your good work.
Kostas
>> > For more options, visit this group at
>> > http://groups.google.com/group/anki-android?hl=en-GB.
>> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "AnkiDroid" group.
> To view this discussion on the web, visit
> https://groups.google.com/d/msg/anki-android/-/lZiNn7gYO8UJ.
>
> To post to this group, send an email to anki-a...@googlegroups.com.
> To unsubscribe from this group, send email to
iniju
Jul 29, 2012, 5:51:43 PM7/29/12
to anki-a...@googlegroups.com
Oh, forgot to say, I'm not expert but it looks fine to me.
Kostas
Tim
Mar 25, 2015, 11:53:24 AM3/25/15
to anki-a...@googlegroups.com
Was this bug eventually fixed in Android? If so, does anyone know from which version we can hide this preference?
Dotan Cohen
Mar 26, 2015, 6:46:28 AM3/26/15
to anki-a...@googlegroups.com
I think that the bug is more complicated than it seems. I notice in
different Android versions (I use 2.1 and 4.4) that there is different
behaviour for Hebrew that is displayed in HTML contexts (such as in
the Ankidroid Show Cards activity) and in native-widget contexts (such
as in the Ankidroid Show Decks activity).
I cannot test the newer Ankidroid versions as they are dropping 2.1
support in favour of Material Design. My gut feeling is that since
older Android version support is being dropped anyway, you might as
well drop this feature as well in the next Alpha rounds. Then you will
have time to know if it really does need to be included before the
betas or a release.
> email to anki-android...@googlegroups.com.
> To post to this group, send email to anki-a...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/anki-android/98efd26f-62ae-458c-bf36-2bd05be7605c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
different Android versions (I use 2.1 and 4.4) that there is different
behaviour for Hebrew that is displayed in HTML contexts (such as in
the Ankidroid Show Cards activity) and in native-widget contexts (such
as in the Ankidroid Show Decks activity).
I cannot test the newer Ankidroid versions as they are dropping 2.1
support in favour of Material Design. My gut feeling is that since
older Android version support is being dropped anyway, you might as
well drop this feature as well in the next Alpha rounds. Then you will
have time to know if it really does need to be included before the
betas or a release.
> --
> You received this message because you are subscribed to the Google Groups
> "AnkiDroid" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> You received this message because you are subscribed to the Google Groups
> "AnkiDroid" group.
> email to anki-android...@googlegroups.com.
> To post to this group, send email to anki-a...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/anki-android/98efd26f-62ae-458c-bf36-2bd05be7605c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Tim
Mar 27, 2015, 1:27:21 AM3/27/15
to anki-a...@googlegroups.com
I was planning on just hiding the preference after a certain version of Android rather than completely removing it...
I took some screenshots with the Android emulator for various API versions using the test page given in the Android issue, but since I can't read Arabic or Hebrew, I'll need someone to check the legibility. I'm not sure what's going on in API15, but at least for API16 (Jelly Bean 4.1) it seems to look good.
API 7 (obviously broken)
API 8 (obviously broken, but better than API 7)
API 15 (looks different from Desktop, but not sure if it's legible or not...?)
API 16 (looks fine to me...?)
API 19+ (looks the same as Desktop to me)
Desktop Chrome (the reference to compare all above to):
> email to anki-android+unsubscribe@googlegroups.com.
Dotan Cohen
Mar 28, 2015, 5:02:11 AM3/28/15
to anki-a...@googlegroups.com
// API 7 (Tim's screenshot)
Regular:
Latin looks fine
Hebrew letters do not display
Arabic letters do not display
Cardo:
Latin as above
Hebrew as above
Arabic as above
// API 8 (Tim's screenshot)
Regular:
Latin looks fine
Hebrew is completely backwards
Arabic is completely backwards
Cardo:
Latin as above
Hebrew as above
Arabic as above
// API 15 (Tim's screenshot)
Regular:
Latin does not appear
Hebrew looks fine without nikud (dots), the dots are placed in the wrong places.
Arabic looks fine
Cardo:
Latin looks fine
Hebrew as above
Arabic as above
// API 16 (Tim's screenshot)
Regular:
Latin looks fine
Hebrew looks mostly fine, but the Shin nikud is in the wrong place in the NFC/D (with cc) table cell.
Arabic looks fine
Cardo:
Latin as above
Hebrew as above
Arabic as above
// API 19+ (Tim's screenshot)
Regular:
Latin does not appear
Hebrew looks fine
Arabic looks fine
Cardo:
Latin looks fine
Hebrew as above
Arabic as above
// Desktop Chrome (Tim's screenshot)
Regular:
Latin looks fine
Hebrew looks fine
Arabic looks fine
Cardo:
Latin as above
Hebrew as above
Arabic as above
Latin looks fine
Hebrew letters do not display
Arabic letters do not display
Cardo:
Latin as above
Hebrew as above
Arabic as above
// API 8 (Tim's screenshot)
Regular:
Latin looks fine
Hebrew is completely backwards
Arabic is completely backwards
Cardo:
Latin as above
Hebrew as above
Arabic as above
// API 15 (Tim's screenshot)
Regular:
Latin does not appear
Hebrew looks fine without nikud (dots), the dots are placed in the wrong places.
Arabic looks fine
Cardo:
Latin looks fine
Hebrew as above
Arabic as above
// API 16 (Tim's screenshot)
Regular:
Latin looks fine
Hebrew looks mostly fine, but the Shin nikud is in the wrong place in the NFC/D (with cc) table cell.
Arabic looks fine
Cardo:
Latin as above
Hebrew as above
Arabic as above
// API 19+ (Tim's screenshot)
Regular:
Latin does not appear
Hebrew looks fine
Arabic looks fine
Cardo:
Latin looks fine
Hebrew as above
Arabic as above
// Desktop Chrome (Tim's screenshot)
Regular:
Latin looks fine
Hebrew looks fine
Arabic looks fine
Cardo:
Latin as above
Hebrew as above
Arabic as above
To unsubscribe from this group and stop receiving emails from it, send an email to anki-android...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/anki-android/620a88a4-fa28-45ae-84b6-c151d8094bcc%40googlegroups.com.
Tim
Mar 28, 2015, 5:18:28 AM3/28/15
to anki-a...@googlegroups.com
Thanks for checking that! Would the issue with API19 cause much annoyance in practice?
To view this discussion on the web visit https://groups.google.com/d/msgid/anki-android/620a88a4-fa28-45ae-84b6-c151d8094bcc%40googlegroups.com.
Tim
Mar 28, 2015, 6:31:51 AM3/28/15
to anki-a...@googlegroups.com
Sorry I meant API16
Dotan Cohen
Mar 29, 2015, 2:39:23 AM3/29/15
to anki-a...@googlegroups.com
For someone who is familiar with the word already, it really isn't a problem. The text is still readable. But for someone who has never seen the word, I could understand that the shifted nikud (dots) may be quite confusing.
Reply all
Reply to author
Forward
0 new messages