Re: Aedict export (supressing the 3rd unnecessary card) -> finally found it
Martin Vysny
I apologize for the late reply, and I'm happy that the export still works for you :-D
I have to admit that I am actually not using the AnkiDroid software since I'm no longer learning Japanese. The new export implementation was thus designed by Tim (the author of AnkiDroid). You can find more information here: http://aedict.eu/faq.html the " Mass export to Anki/AnkiDroid?".
I will try to explain how I think it works. Instead of the old system of exporting the front/back information to AnkiDroid, Aedict will now export the "semantic" information about the entry: Reading, Kanji, Sense, etc. All of this information is saved to the AnkiDroid database when you export entries from Aedict.
Now, AnkiDroid of course needs to display the card front/back from that info - it needs rendering rules on how to render front/back from the "Reading", "Kanji", "Sense" fields. That is now done by defining the card model in AnkiDroid. For example Aedict will create a "sk.baka.aedict3v6" card model, which contain three card types:
Meaning->Kanji/Reading
Kanji->Reading/Meaning
Kanji/Reading->Meaning
Every card type has its own rules on how to draw the card front and the card back. You can edit those rules in AnkiDroid and change them in any way you wish, you can define your own card types, etc. This new concept is quite powerful, but it's probably not so easy to understand. Yet, that's something I can do nothing about: that's the decision made by the AnkiDroid guys.
I think that AnkiDroid allows you to select card type shown when you start your card review, but I don't know for sure. This is something that is best explained by the AnkiDroid guys.
Thanks!
Best regards,
Martin
Hello again,
after continuing to search for these fields, I finally found it. When I add new cards, there all the way down it is below the tag field.
Apparently it sticks for other decks then too, not exactly intuitive but at least it seems to work now with two cards only, although that one introduces the issue that to any given Kanji term, the reading is given as well, so no learn effect here. :(
But since this is probably beyond your scope of Aedict, when in doubt I better create a new thread with Tim then I guess.
My export question is still valid though.
Best regardsJoshua Winter
On 7 May 2017 17:14, "Joshua Winter" <yosh...@gmail.com> wrote:
Hello Martin,
we have been in contact a while ago because of the export issue to AnkiDroid if you remember.
The good news is that I just updated both Aedict and AnkiDroid to the most recent versions (3.39.35 and 2.8.2 respectively keeping my fingers crossed) and the export is still working (although the additional permission stays unchecked for Aedict) - strange but anyway.
However, I'd need your support in another way, concerning the export:
I also face the issue described here:
There, you're referring to editing some Aedict card model and some ID callled sk.baka.aedict3v6. Unfortunately though, I have absolutely no idea where and how to do that. I've got root access but don't know what file maybe to edit or what option to change in Aedict or AnkiDroid.
Would be great if you could point me to the right direction, thanks.
As for general understanding: why isn't it possible to change Aedict's export behaviour in the first place?
Best regardsJoshua
On 13 Feb 2017 15:54, "Martin Vysny" <vy...@baka.sk> wrote:
Hi Joshua,
that's some valuable info you found out. Can you please add exactly this info here: https://github.com/mvysny/aedict/issues/723 ? We can also discuss possible solutions there. Or we can continue to discuss this at the Aedict mailing list: aedict...@googlegroups.com
Thanks!
Best regards,
Martin
On 13.02.2017 08:31, Joshua Winter wrote:
Hi Martin,
me again – guess what, this is becoming stranger and stranger. Now I did the following test: I uninstalled AnkiDroid 2.8.1 and grabbed the 2.7 APK from GitHub, installed it and checked if the permission persists this time.
As expected, it doesn’t – once I tick it, it becomes unticked again. L
BUT: the export from Aedict actually works nonetheless (no crash, and entered in the deck in AnkiDroid).
Then I updated AnkiDroid directly via the Play Store to 2.8.1 again and – it continues to work.
Something seems to be really screwed up with the permissions. Since I use both of them quite often, maybe we should create a group chat to have investigated further.
I’ll be certainly of assistance and willing to test any (beta) apks you want to provide.
Cheers,
Joshua
From: martin...@gmail.com [mailto:martin...@gmail.com] On Behalf Of Martin Vysny
Sent: Monday, February 13, 2017 2:09 PM
To: Joshua Winter <yosh...@gmail.com>
Cc: aedict-users <aedict...@googlegroups.com>
Subject: Re: Aedict Anki export permission not sticky anymore under Nougat UK BTU build
Hi Joshua,
The permission being not sticky reminded me of this issue:
This seems like a bug in Android, unfortunately there is not much I can do. Maybe you can convince Tim of Ankidroid to drop the requirement of that particular permission? Maybe Android for some reason (a bug) unchecks only app-specific permissions? That is, the SD card related permission is a android built-in permission which thus works correctly, while the Ankidroid custom permission gets reverted by android?
Best,
Martin
On Feb 13, 2017 03:36, "Joshua Winter" <yosh...@gmail.com> wrote:
Hello Martin,
updating recently to yet another newer Nougat build (G930FXXU1DQB3), this time I was successfully able to restore Aedict without asking for the dictionary files. While you're right that TitaniumBackup excludes them from the backup, I originally had taken that into account by copying them manually. So maybe something else went wrong the first time.
However, I just encountered a new issue:
Trying to export an entry to Anki, Aedict crashed again. Remembering having to allow the access in the permissions section, I tried to do exactly that. This time though, while the entry still exists, it isn't sticky. As soon as I leave the menu, the slider is to the left (disabled) again. Stopping Aedict before trying to set the access right or completely reinstalling it from scratch doesn't help either. :(
I also restarted the phone but no avail, the already set storage permission is sticky, but the important one is not.
Not sure if that's related to the update to the even newer Nougat build.
Regards
Joshua