AnySoftKeyboard 🚀 - missing Keyboards on f-droid

Portuguese is also missing but probably we should tell F-droid

moshpirit on 13 Aug 2016

I thought that Software developer have to put their software to the stores.

Mannshoch on 20 Aug 2016

@Mannshoch if the repo is set up correctly F-droid can do all the work.

grrrrr on 25 Aug 2016

👍2

Hey, I was missing the German pack as well and it seems other folks are too (see https://github.com/AnySoftKeyboard/LanguagePack/issues/10 and https://f-droid.org/forums/topic/anysoftkeyboard-language-packs-layouts-plans/). So I went to the Google Archives at https://code.google.com/archive/p/softkeyboard/source/default/source and downloaded the SVN dump. I was easily able to build an APK for the German pack. There are other packs as well (I didn't try them out):

[ ] Arabic
[x] Armenian
[x] Belarusian
[x] Bulgarian
[x] BulgarianLarge
[ ] Catalan
[ ] Cherokee
[x] Czech
[x] Danish
[ ] Devanagari
[ ] Dhivehi
[x] Dutch
[x] EnglishDictionary
[ ] Esperanto
[x] Finnish
[x] French
[x] FrenchLarge
[x] FrenchXLarge
[ ] Fulah
[ ] Georgian
[x] German
[x] Greek
[ ] Hawaiian
[x] Hebrew
[x] HebrewLarge
[x] Italian
[ ] Kannada
[ ] Lao
[x] Latvian
[x] Lithuanian
[x] Norwegian
[ ] Persian
[x] Portuguese
[x] Russian
[ ] Sindhi
[x] Slovak
[x] Slovene
[x] Spain
[x] Swedish
[ ] Swiss
[ ] Tamil
[x] Terminal
[ ] Thai
[x] Ukrainian

As far as I can see, in F-Droid are these:
Danish
Esperanto
French
Georgian
Greek
Hebrew
Lithuanian
Magyar
Malayalam
NEO2 (Neo2 Keyboard Layout)
Pali
Persian
Spanish
SSH
Ukrainian

So it might be worth resurrecting the others from the SVN? I would volunteer to try to, if this is still of interest here? @menny would you merge them here?

friesenkiwi on 12 Dec 2016

I'll gladly accept PRs!

The process should be as follow:
1) uplift the pack's source code to the latest base: https://github.com/AnySoftKeyboard/LanguagePack/
2) create a PR and point it to be merged to a specific branch, for example, if you want to merge the German pack, I'll first need to create a branch for it.

Do you think you can do that?

menny on 12 Dec 2016

Hey, you answered so fast I nearly missed it, sorry :-)
Yes, I think I should be able to do it this way. The version history and authors of the SVN will be lost though :-( I was trying to import the SVN dump via git-svn but it refused to recognize the dump as local repository, so it wasn't working anyway.
I would create branches for all languages that work in my fork and raise you here again, so you can create the branches in your original upstream repo, OK?
It might take a couple of days, though, need to find the time.
Is it easy to but those resurrected language packs on F-droid then?

friesenkiwi on 14 Dec 2016

History is not that important 😃

Yes, please ping me before submitting a PR, and I'll create the required branches.
Thanks for doing this! 💪

menny on 14 Dec 2016

Ok, I had a go with the German one:
https://github.com/friesenkiwi/LanguagePack/tree/German
I never had any contact with android keyboards before, so I'm very unsure if I converted it the right way, especially regarding the dictionary generation...?
Please check thoroughly, whether this is OK from your perspective.
I installed it on my phone though and it seems to work as usual.

friesenkiwi on 14 Dec 2016

Hey @menny did you have time to have a look on the port of the German pack? I'd go ahead with the others, if this was fine. Also, will we be able to put those packs into F-Droid?

friesenkiwi on 29 Dec 2016

@friesenkiwi it seems like a good start.
I would suggest two things:
1) rebase from _master_, I'm updated it yesterday
2) after rebasing, replace the mp3 dictionary with a AOSP dictionary (there is a new GenerateWordsListFromAOSPTask task!)

menny on 29 Dec 2016

done (though somehow unlcean... ;-))
Sorry, I don't understand what you mean or how to do it? In Android Studio, I can't see a "GenerateWordsListFromAOSPTask" in the AnySoftKeyboard/LanguagePack project.
Do you mean, there has to be something changed in the build.gradle, in the parseAospForEnglishDictionary part? I changed that, but this task always fails silently without error message. :-(

friesenkiwi on 30 Dec 2016

Would it be possible for you to create a smaller German keyboard when you are at it (without äöüß) I hope this is not too much out of context,.and there will be a German keyboard on fdroid soon :)

benneti on 30 Dec 2016

@friesenkiwi check out https://github.com/AnySoftKeyboard/LanguagePack/blob/master/build.gradle#L58
this is a new gradle task taht generates a dictionary form AOSP words-list.
I've used that in the Hebrew language-pack: https://github.com/AnySoftKeyboard/LanguagePack/commit/55203d2d3acd305abedaf0cb12cb798d7a2b7536#diff-c197962302397baf3a4cc36463dce5eaR50
and in the main-apk English's dictionary: https://github.com/AnySoftKeyboard/AnySoftKeyboard/commit/9b8a2be4f85b44711d1814b2ff9ff264ebc2677c#diff-c197962302397baf3a4cc36463dce5eaR54

Using this technique, will generate a really awesome German dictionary.

menny on 30 Dec 2016

@menny Aaah, now I'm getting it, thank you for the links to diffs. :)
I amended the build.gradle accordingly and added the german dictionary from here: https://android.googlesource.com/platform/packages/inputmethods/LatinIME/+/master/dictionaries/de_wordlist.combined.gz?format=TEXT, (see https://github.com/friesenkiwi/LanguagePack/commit/51bbf260f8186e3e4867d2a6226dde55c4fff1a1).
But unfortunately the gradle task fails:

Executing tasks: [clean, :generateDebugSources, :generateDebugAndroidTestSources, :mockableAndroidJar, :prepareDebugUnitTestDependencies]

Configuration on demand is an incubating feature.
Incremental java compilation is an incubating feature.
The TaskInputs.source(Object) method has been deprecated and is scheduled to be removed in Gradle 4.0. Please use TaskInputs.file(Object).skipWhenEmpty() instead.
:clean
:preBuild UP-TO-DATE
:preDebugBuild UP-TO-DATE
:checkDebugManifest
:preReleaseBuild UP-TO-DATE
:prepareComGithubAnySoftKeyboardAnySoftKeyboardAPI170Library
:prepareDebugDependencies
:compileDebugAidl
:compileDebugRenderscript
:parseAospForGermanDictionary
Reading input file aosp_de_wordlist.combined (size 1724568)...
.100%.Sorting list of 0 words...
Wrote 0 words.
Done.
:mergeAllWordLists
Merging 1 files for maximum 300000 words, and writing into 'words_merged.xml'. Discarding 0 words.
Reading words_from_aosp.xml...
Loaded 0 words in total...
Sorting list...
Creating output XML file...
Wrote 0 words.
Done.
:makeDictionary
Reading words from input .../LanguagePack/dictionary/words_merged.xml
Will store output files under .../LanguagePack/src/main/res/raw
Deleting previous versions...
Nodes = 1
Dict Size = 0
:makeDictionary FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':makeDictionary'.

java.io.IOException: Failed to create binary dictionary file. Size zero.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 0.651 secs
Executing tasks: [clean, :generateDebugSources, :generateDebugAndroidTestSources, :mockableAndroidJar, :prepareDebugUnitTestDependencies]

Configuration on demand is an incubating feature.
Incremental java compilation is an incubating feature.
The TaskInputs.source(Object) method has been deprecated and is scheduled to be removed in Gradle 4.0. Please use TaskInputs.file(Object).skipWhenEmpty() instead.
:clean
:preBuild UP-TO-DATE
:preDebugBuild UP-TO-DATE
:checkDebugManifest
:preReleaseBuild UP-TO-DATE
:prepareComGithubAnySoftKeyboardAnySoftKeyboardAPI170Library
:prepareDebugDependencies
:compileDebugAidl
:compileDebugRenderscript
:parseAospForGermanDictionary
Reading input file aosp_de_wordlist.combined (size 1724568)...
.100%.Sorting list of 0 words...
Wrote 0 words.
Done.
:mergeAllWordLists
Merging 1 files for maximum 300000 words, and writing into 'words_merged.xml'. Discarding 0 words.
Reading words_from_aosp.xml...
Loaded 0 words in total...
Sorting list...
Creating output XML file...
Wrote 0 words.
Done.
:makeDictionary
Reading words from input ...LanguagePack/dictionary/words_merged.xml
Will store output files under ...LanguagePack/src/main/res/raw
Deleting previous versions...
Nodes = 1
Dict Size = 0
:makeDictionary FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':makeDictionary'.

java.io.IOException: Failed to create binary dictionary file. Size zero.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 0.651 secs

For some reason, it seems to not be able to parse the wordlist:

Reading input file aosp_de_wordlist.combined (size 1724568)...
.100%.Sorting list of 0 words...

Can you have another look?

@benneti I'd say it should be possible (although the additional keys are somewhat my reason for needing a special german keyboard... ;-)). But I'd like to get the current version into upstream first, then all the other missing languages and after that, I'm open to looking into removing the äöüß keys. We probably should do this in a different Issue, though.

friesenkiwi on 31 Dec 2016

It took me a while but I was finally able to build a German keyboard (mit Umlauten).

A few findings: It seems that the build process (maybe generatewordslist-1.0-SNAPSHOT.jar) is not able to transform any .combined wordlists into .xml wordlists. So I was looking for an .xml wordlist and finally found this:

https://github.com/mozilla-b2g/gaia/blob/master/apps/keyboard/js/imes/latin/dictionaries/de_wordlist.xml

I fetched the repo from:

https://github.com/friesenkiwi/LanguagePack/tree/German

And copied de_wordlist.xml (and some other, empty files (see build.gradle)) to dictionaries.

Then I did a dirty hack with build.gradle (find it attached).

But finally the build finished (that is all that counts for me).

Feel free to use my findings to set up a proper build process and/or feel free to use the attached apk.

Greetings.

build.gradle.zip
LanguagePack-debug.german.apk.zip

motatuc on 19 Jan 2017

👍1

Thanks for all this work.
I'll be happy to see it in f-Droid.

Mannshoch on 20 Jan 2017

Hey @motatuc, thank you for your work and suggestion. I included some of the changes from your attached build.gradle over at my branch and also the .xml you mentioned, and yes, the build now works! :-)
But, I would like to use the "standard" way (GenerateWordsListFromAOSPTask / aosp_de_wordlist.combined), I only don't know, why that fails (as described above).
@menny do you have any idea or suggestion?

friesenkiwi on 21 Jan 2017

@friesenkiwi where I can pull your code?

menny on 21 Jan 2017

It's at https://github.com/friesenkiwi/LanguagePack/tree/German

friesenkiwi on 21 Jan 2017

@friesenkiwi I found the issue. The combine file you used is in the wrong format. I don't know how that happened, but essentially, I've downloaded the entire dictionaries folder, and then unziped the de file. When I view the unzipped file in a text editor, I saw something like:

dictionary=main:de,locale=de,description=Deutsch,date=1414726263,version=54,REQUIRES_GERMAN_UMLAUT_PROCESSING=1
 word=der,f=216,flags=,originalFreq=216
 word=und,f=213,flags=,originalFreq=213
 word=die,f=211,flags=,originalFreq=211
 word=in,f=208,flags=,originalFreq=208
 word=von,f=204,flags=,originalFreq=204
.....
....

So, I replaced the file you have on your repo with the correct one, then I created the target folder src/main/res/raw and ran the generate dictionary task: ./gradlew makeDictionary

This produced a very large DE dictionary.

I've attached the revised build.gradle file and the correct de_wordlist.combined file.
Archive.zip

menny on 22 Jan 2017

@friesenkiwi I've updated the Gradle tasks in AnySoftKeyboardTools to automatically create the raw folder. And I've updated the master branch of LanguagePack to reflect that change.

You may want to rebase your branch to latest master.

menny on 22 Jan 2017

Sorry to hijack this thread, but is there currently a place to download the German language pack, installable Apk for non-developpers? The one available from the Play Store is old and not really that good.

Larx on 22 Jan 2017

Sorry if I'm hijacking this thread, but where can I find the code for the Swedish layout?

lindhe on 22 Jan 2017

Easy, guys :-)

@menny thank you very much, that did it! I have no idea, how I got this mixed up aosp_de_wordlist.combined, but anyway, now it works. And now the file and the whole process makes much more sense to me.
I also rebased as you suggested and made some small alterations.
So for me it looks fit to be merged into upstream as a new branch.
I will make a pull request, if you create the according branch.
What's left after that to put it into the official F-Droid-Repo?

@Larx for the time being, I put the release apk into my own F-Droid Repo at https://fdroid.denk-nach-mcfly.de/fdroid/repo/, or the direct link to the APK is https://fdroid.denk-nach-mcfly.de/fdroid/repo/LanguagePack-release.apk

@lindhe the code for the swedish pack should be amongst the others over at the archive of the old project at: https://code.google.com/archive/p/softkeyboard/source/default/source. You would need to download the whole svn dump and it may compile directly. But as soon as this work on the German layout is finished, I plan to resurrect also all the other "missing" packs (as indicated above) to make them available in F-Droid, so if you can wait for another couple of weeks, the problem should be solved! :-)
Or, you can of course also help out and do the work discussed above and reflected in my branch, to build a 'modern' swedish pack and we split the work.

Cheers

friesenkiwi on 22 Jan 2017

👍1

@friesenkiwi branch created: https://github.com/AnySoftKeyboard/LanguagePack/tree/German
Please send a PR over

menny on 23 Jan 2017

Thanks for the download link! The new German keyboard is much better than the old one currently available "officially".
Will the direct download link always provide the latest version?
And: Why does it identify itself as "Deutsch-Sweizerdeutsch" :-) ?

Larx on 23 Jan 2017

Could be interesting how they implemented Swiss-German. on the Hardware Keyboard for swiss Germans the öäü Key contain also éàè and [{

Also Swiss-German speaker write their SMS in their Urban language Swiss-German.
(which differ really heavy between their dialect)

As far it appears on f-droid I'ill try this.

Mannshoch on 23 Jan 2017

@Larx thanks, that's probably because of the new way to create the dictionary from the AOSP sources. And no, as soon as this lands on Play Store/official F-Droid, i'll probably remove the APK from my own repo, since it isn't necessary anymore and might only confuse. This was only a quick hack for the time being.
Actually, the "Sweizerdeutsch" typo was in the old sources and I fixed it in the new version (see https://github .com/AnySoftKeyboard/LanguagePack/blob/German/src/main/res/values-de/strings.xml), if it still displays so to you, there might be some kind of cache in action. Maybe rebooting or uninstall/install would fix this. But see below.
@Mannshoch Thank you for raising the attention towards this. I'm afraid there is no special swiss dictionary and also the layout does not correlate with what I see here: https://de.wikipedia.org/wiki/Tastaturbelegung#Schweiz, so the description "Schweizerdeutsch" is totally misleading, if not wrong. I will remove it as a first step. The right way to handle this may be an extra swiss keyboard, then also using a different source for the dictionary. Do you have any idea or suggestion where to get one or texts containing such urban dialectic words, which could be used to generate it?

friesenkiwi on 24 Jan 2017

@friesenkiwi, thanks for your efforts on that matter.

About the "Umlaute": Is it possible to have a keyboard where the Umlaute only appear on longpress (like it is with the google keyboard)? Ideally the space gained from hiding the Umlaute leads to slightly bigger keys...

Is this easily changeable in the source?

motatuc on 24 Jan 2017

@friesenkiwi I forgott an other situation here. Swiss German (de_CH) is also a special Dictionary because "Swiss Standard German" do not contain ß and its also missing on Keyboards.
EN: https://en.wikipedia.org/wiki/Swiss_Standard_German#Written_Swiss_Standard_German
DE: https://de.wikipedia.org/wiki/Schweizer_Hochdeutsch#Schriftliche_Verwendung

Mannshoch on 24 Jan 2017

@motatuc I'm new to keyboards and dictionaries and therefore didn't want to experiment but first simply make the old/original version available via F-Droid. This seems not to have worked entirely though ;)

You are also not the only one asking for a "smaller" keyboard with the dedicated umlaut keys replaced by a long press popup (see @benneti https://github.com/AnySoftKeyboard/AnySoftKeyboard/issues/690#issuecomment-269797767, https://github.com/AnySoftKeyboard/LanguagePack/issues/4 or some comments at https://play.google.com/store/apps/details?id=com.anysoftkeyboard.languagepack.german)

From looking at the source at https://github.com/AnySoftKeyboard/LanguagePack/blob/German/src/main/res/xml/keyboards.xml and https://github.com/AnySoftKeyboard/LanguagePack/blob/German/src/main/res/xml/de_qwerty.xml it looks, as if it may be quite easy, so I'll try. But I don't know about the selection/switching in AnySoftKeyboard.
@menny, can you shed some light? If I now add a new element to keyboards.xml and create the according de_querty_condensed.xml, how would those two keyboards be selectable in the UI? I'd rather don't have it in the first level toggle directly on the keyboard, because that would clutter my own workflow. Or is there any other option to make it configurable? Surely, an entirely new .apk shouldn't be the way.

@Mannshoch regarding the swiss layout, that should be doable (also removing ß), but for the dictionary there would need to be some texts to generate it from. In the old SVN dump there is a swiss LanguagePack, but it doesn't contain any dictionaries.

Gee, I didn't think that there would be so many edge cases here...

friesenkiwi on 24 Jan 2017

Some comments at https://github.com/AnySoftKeyboard/LanguagePack/pull/27 and a new PR at https://github.com/AnySoftKeyboard/LanguagePack/pull/28

friesenkiwi on 24 Jan 2017

Tryed som websearch for dictionaries. Maybe it helps you so you have not to do extra modifications. I would prefer language tool. I use it in Firefox and LO on my Windows machine.

Dictionarys:

Hunspell: https://cgit.freedesktop.org/libreoffice/dictionaries/tree/de
Aspell: ftp://ftp.gnu.org/gnu/aspell/dict/de/
Firefox Dictionarys: https://addons.mozilla.org/en-US/firefox/language-tools/
Languagetool: https://github.com/languagetool-org/languagetool/tree/master/languagetool-language-modules/de/src/main/resources/org/languagetool

Mannshoch on 24 Jan 2017

Thanks! But I think this would mean quite some work to make it compatible to ASK...? @menny is the only one who can tell. But I'll suggest we do one thing after the other: First a current de_DE APK in Play store and F-Droid, afterwards new packs, OK?

friesenkiwi on 24 Jan 2017

No problem. Do as you think it's best. I'm not a developer but if I could help and support I'll do it.

Mannshoch on 24 Jan 2017

@friesenkiwi, I managed to build a nice German keyboard layout without the Umlaute. They only appear on longpress now.

Find the edited de_qwerty.xml attached.

de_qwerty.xml.zip

And for test purposes, find the apk attached.
LanguagePack German

motatuc on 25 Jan 2017

@motatuc yes, that looks quite like I suspected above, thank you for the tryout. But you included all kinds of special characters and digits as well, do you think is there a use case for them on a German keyboard? I'd rather keep it as clean as before...
And we still need to figure out, how to switch between styles...

friesenkiwi on 25 Jan 2017

I just copied the special keys from the English layout. But yes, this is a lot of special characters. Less of them would also do it, because I don't see real daily-life usecases for them. :)

Feel free to modify and push a new version as you like.

motatuc on 27 Jan 2017

I think @ on a and numbers on first row should stay as they are very comfortable, actually I think they all could stay as long as they are in a reasonable order, so they don't interfere with typing habits (first button on vocals on a German layout should be the appropriate umlaut after this on a: @ on euio: the corresponding number).
Also the german input does not work with experimental gesture support (but I don't know wetter this is a problem in the keyboard or its not possible ATM).

Thanks for your work to get this on f-droid :)

benneti on 27 Jan 2017

I have to correct myself: the newer build wich is already on fdroid makes it possible to use gesture typing.

benneti on 28 Jan 2017

@Larx fyi, the the German pack is back in Play Store and F-Droid with a new dictionary.

So, after that, we can now work on improving it and re-adding the other missing packs.

@menny I resurrected the Swedish pack (due to demand by @lindhe) in the same way as before, please find it at https://github.com/friesenkiwi/LanguagePack/tree/Swedish, check, and in case you're satisfied, create the Swedish branch so I can make the PR?
I do not speak Swedish, so the translations are missing, maybe someone else might be able to do them and the screenshot?
(For trying out, the APK is in my F-Droid at https://fdroid.denk-nach-mcfly.de/fdroid/repo/LanguagePack-release_sv.apk)

The next pack might become Portuguese (due to demand by @moshpiri).

@motatuc @benneti thank you for your suggestions, I now incorporated two more keyboards in the German pack, both are a little bit "broader" because the üöäß keys are replaced by popups, the second one even has all the additional characters and numbers.
Please check the version at https://fdroid.denk-nach-mcfly.de/fdroid/repo/LanguagePack-release_de.apk, if those fulfill your requests, I will put up a new PR.
One can activate the layouts in ASK's global settings, so everyone can decide freely, what best fits their workflow.
Similar request was by @JuNo13 at https://github.com/AnySoftKeyboard/LanguagePack/issues/4, which could be closed, as soon as this new changes would be merged.

@benneti thank you for testing gestures, I wasn't considering them specially, but glad it works.

@Mannshoch I suspect the Swiss pack could become quite interesting. Probably the keyboard should look like discussed above, that should be quite easy. But there would be need of a German, French, Italian and additional special Swiss-German dictionary included, all merged together? Or would you rather install the German, French and Italian packs?

So, this looks like a fair amount of work, I'd appreciate it if anybody would join forces...?

Cheers,
Hanno

friesenkiwi on 28 Jan 2017

👍1

Thank you for your effort (but i can't do much else than testing to help you).
Are you able to choose the order of the special keys?
If yes, then I would make the umlaute äüö the first/default one and the number directly next to it for ease of access.
Also you can't type words with äöü with gestures when they are not visible, but I think that is a ask problem, should I open a new issue for this?
Lasty I want to ask is wether it is purpose that the second and third line are a bit broader than on the QWERTY keyboard.

benneti on 28 Jan 2017

Yes, the order can be changed (see https://github.com/friesenkiwi/LanguagePack/blob/German/src/main/res/xml/de_qwertz_extra.xml), and my first test had üöä first, but then I thought it might be beneficial to have the numbers first as a "rule" (since they are on each key of the first row), then üöä/special chars, then all the other chars like â etc.. Actually I would personally vote for completely removing the numbers, since you can swipe upwards for them or quickly switch to the numbers/specialchars keyboard.

I guess this is only a matter of taste, so @motatuc @Larx @JuNo13 @Mannshoch (and anyone else with an opinion about this), what are you saying:

Current: 1@, 3€è..., 6ż..., 7üù..., 8ì..., 9öò...
Umlauts/special chars first: @1, €3è..., 6ż..., ü7ù..., 8ì..., ö9ò...
Loose the numbers: @, €è..., ż..., üù..., ì..., öò...
?

Yes, I widened the keys in the second and third row on purpose, since the whole point in removing the umlaut keys was to make more room and make it easier to hit the other keys. So I consider it to be consequent, not to leave any lost room on the keyboard, even if this might not be totally symmetric and aesthetically pleasing to everybody ;-) This is how it looks on my device (S4 Mini), does it look different on your's?
screenshot_20170128-160016

About the gesture typing with umlauts/popup characters: Yes, that would probably be an issue over at https://github.com/AnySoftKeyboard/AnySoftKeyboard/issues/new. But to bypass the problem, you could use the layout with the specialized keys ;-)

friesenkiwi on 28 Jan 2017

Yes, I noticed the new versions on PlayStore and FDroid, very appreciated!
A few questions:
In the dictionaries (autocompletion), the umlauts seem to be treated separately from their non-dotted brethren. E.g. typing uber should intuitively propose über, but this is not the case.
Is it possible to have a variation of the keyboard which is kind of right-aligned,for better one-handed usage on bigger screens?
The long-press alternatives are displayed very small on the keyboard.
Is it possible to have German layout with English dictionary? On my desktop, I don't change keyboards when typing in another language.

Thanks for your work!

Larx on 28 Jan 2017

Those questions all seem to result in separate new issues over at https://github.com/AnySoftKeyboard/AnySoftKeyboard/issues/new, I'm sorry.

Autocompletion: Yes, I can confirm the non-suggestion between umlaut/non-umlaut words/characters, but I have no idea why, if it's related to the dictionary or what else. I would suspect, that this behaviour should be the same in e.g. french or spanish packs?
Special treatment of large screens for one-handed usage would probably better be implemented as a configurable general feature
Popup size: The same goes for this
Arbitrary combination of keyboard layout and dictionary: This has been asked a couple of time already, see https://github.com/AnySoftKeyboard/AnySoftKeyboard/issues/832, https://github.com/AnySoftKeyboard/AnySoftKeyboard/issues/617, https://github.com/AnySoftKeyboard/AnySoftKeyboard/issues/582 (as a sidenote, on your desktop, you can actually switch the keyboard layout pretty easily via task bar/notification area, and you generally don't use dictionaries/suggestions, so the comparison is somehow unfair ;-))

friesenkiwi on 29 Jan 2017

I see, your probably right.

Larx on 29 Jan 2017

here my testing result of this keyboard.
screenshot_2017-01-30-08-32-45
and
screenshot_2017-01-30-08-33-25

Mannshoch on 30 Jan 2017

Thanks for your images.

I have no idea, where the space below comes from. Seems like a totally separate issue?
Looks like you don't have the latest dev version installed. Can you uninstall and install from https://fdroid.denk-nach-mcfly.de/fdroid/repo/LanguagePack-release_de.apk ?
If I understand you correctly, you are voting for option 3 from https://github.com/AnySoftKeyboard/AnySoftKeyboard/issues/690#issuecomment-275853048?

friesenkiwi on 30 Jan 2017

@menny can you make a new Swedish branch for the PR?

friesenkiwi on 30 Jan 2017

Some more observations:
If there is a word which can be used as noun (capital letter) or not (small letter), ASK will always only propose the alternative with small letter. E.g. "morgen" vs. "Morgen". Maybe some general incompatibility with a German speciality?
Some very common words seem to miss from the dictionary, I had to add "für", "wünsche" or "Übergabe" for example. Now that I think of it, don't know if its pure chance, umlaut problem?!

Larx on 31 Jan 2017

I prefer #2 more then #3

Mannshoch on 31 Jan 2017

I would prefer #2, too

benneti on 31 Jan 2017

@friesenkiwi branch created: https://github.com/AnySoftKeyboard/LanguagePack/tree/Swedish
Sorry for being late, I'm travelling.

menny on 1 Feb 2017

@menny if you like, there's a resurrected Norwegian branch ready at https://github.com/friesenkiwi/LanguagePack/tree/Norwegian ;-)

friesenkiwi on 3 Feb 2017

@friesenkiwi can I send you an invite to ASK Slack channel?

menny on 3 Feb 2017

I don't have a Slack account and was hoping to be able to evade that next platform... what about a Jabber Group Chat? :-)
Nah, OK, I see it makes life easier so I'll agree over a reluctant sigh ;-) Can you send via PM? Or do you need something from me fo that?

friesenkiwi on 3 Feb 2017

I don't think github has PMs. right?
You can email me (my email address is on my profile here at github), and we'll continue there.

menny on 3 Feb 2017

Or, we can continue here. I don't mind.

menny on 3 Feb 2017

You can send a PR for Norwegian to here: https://github.com/AnySoftKeyboard/LanguagePack/tree/Norwegian

menny on 3 Feb 2017

PR sent.

If you are OK with it, I'm fine with continuing here?

friesenkiwi on 3 Feb 2017

That works for me too.

menny on 3 Feb 2017

@menny please create new branches for Finnish, Italian, Latvian, Russian and Slovene. I already initialized those branches over at my fork and resurrected the SVN resources, also in the case of Latvian included fixes for #586 and #587, and in the case of Slovene added a completely new keyboard. Since I can't speak, write or read any of those languages, I hope everything worked out well and there are a few string translations missing. I aimed to follow a standard scheme so all the packs differ only in small potions from each other.