Anysoftkeyboard: Doubts about rewrite of Esperanto language package

[Porrumentzio]

Hi all! We're planning to rewrite the Esperanto Language package (both layouts and dictionary) and we have some questions:

1) How many layouts could we add? Esperanto speakers are through all around the world, so we plan to add the most common latin-layouts (QWERTY, QWERTZ, AZERTY, Colemak, Dvorak, Workman, Bepo...)

2) Is it possible to add the emojis as a pop-up key? I think emoji's android:code is "-10". Is there any list where we could see those codes? For Unicode/HTML codes isn't a problem, as they're very common

3) For pop-up characters, is there any logic to determine which character (first, second, third...) will be exactly above the original key? Seems that sometimes is the first, other times the third...

4) Is it possible to see the changes made on the layouts, with Android Studio or with other tool, before PR? Or will we have to wait for the publication for Android devices?

[menny]

thank you for your efforts!

1. I don't think there is a hard limit. Technically, you can add thousands (but now that you mention that, I'm going to introduce logic that limits that to 32). I would say that adding more than 5 or 6 can be overwhelming to non-technical people.
2. you can see the API values of the codes here or here. Does that answer your question?
3. we try to position the first popup character above the pressed key. If there is not enough space (because the pressed key is at the edge), we will reverse the order (left->right will become right->left) and try again. If that does not help, then it's just random.
4. You can compile your pack, and install it on a device running AnySoftKeyboard. That's what I do. I do not have a visual editor.

[Porrumentzio]

Hey, thank you for answering!

1) You're right, we will take that into account and, at most, introduce 6-7 (as the esperantist community is really diverse)

2) I've looked into those values and they're really useful. I haven't found the emojis' value though. Is with another name?

3) Understood. We could make an idea about how it would be for us, though the best will be to try it out.

4) Maybe we will ask for help in the future, but I think its not mandatory to see the layouts, as they're easily predictable.

Great thanks for your help!

[menny]

emojis are quick-text addons.
So, QUICK_TEXT will output the default emoji and QUICK_TEXT_POPUP will open the popup of all emojis

[Porrumentzio]

Hi again!
I have another doubt: if we add some other layouts (let's say dvorak.xml on /src/main/res/xml/) should we create another <keyboard (...) /> structure on ~/res/xml/keyboards.xml and complete it?

There are some parameters, as iconResId and defaultDictionaryLocale, which would be same for all layouts.
But the other parameters should change, right? layoutResId should be "@xml/dvorak.xml", and the description should be consequent.

Lastly, should we add <string name="keyboard_name">dvorak</string> on ~/res/values/strings.xml and generate a new UUID and paste in into keyboards.xml right place (id)?

[Porrumentzio]

About wordList creation to make _dictionaries_, we want to follow this guide: https://github.com/AnySoftKeyboard/AnySoftKeyboardTools/blob/master/README.md#how-to-use-1

But we get this error when trying to build:

Could not find method inputTextFile() for arguments [/home/porru/Sorkuntza/GNU/GIT/AnySoftKeyboard/ASK-eo/LanguagePack/dictionary/eblaj-vortoj - esperantilo.org.txt.txt] on task ':parseOpenOffice' of type com.anysoftkeyboard.tools.generatewordslist.GenerateWordsListTask.

Is there any other way to make this properly?

[menny]

Hi again!
I have another doubt: if we add some other layouts (let's say dvorak.xml on /src/main/res/xml/) should we create another <keyboard (...) /> structure on ~/res/xml/keyboards.xml and complete it?

This is correct.

There are some parameters, as iconResId and defaultDictionaryLocale, which would be same for all layouts.
But the other parameters should change, right? layoutResId should be "@xml/dvorak.xml", and the description should be consequent.

correct again.

Lastly, should we add <string name="keyboard_name">dvorak</string> on ~/res/values/strings.xml and generate a new UUID and paste in into keyboards.xml right place (id)?

Yes, each keyboard layout should have a unique UUID

[menny]

About wordList creation to make _dictionaries_, we want to follow this guide: https://github.com/AnySoftKeyboard/AnySoftKeyboardTools/blob/master/README.md#how-to-use-1

But we get this error when trying to build:

Could not find method inputTextFile() for arguments [/home/porru/Sorkuntza/GNU/GIT/AnySoftKeyboard/ASK-eo/LanguagePack/dictionary/eblaj-vortoj - esperantilo.org.txt.txt] on task ':parseOpenOffice' of type com.anysoftkeyboard.tools.generatewordslist.GenerateWordsListTask.

Is there any other way to make this properly?

That repository is archived and closed. You should follow the instructions in this repository: https://github.com/AnySoftKeyboard/AnySoftKeyboard/blob/master/addons/CONTRIBUTING.md

[Porrumentzio]

Okay, we'll follow that guide. Anyway is quite confusing to have three repositories ( https://github.com/AnySoftKeyboard/AnySoftKeyboard/tree/master/addons/languages, https://github.com/AnySoftKeyboard/LanguagePack and https://github.com/friesenkiwi/LanguagePack/ ), though some being deprecated.
Maybe it would be good to merge all the necessary data into one and remove the other, cause it causes problems to find the real one when searching through the internet. :)

[Porrumentzio]

I'll be posting my doubts here and it would be great to concrete more the CONTRIBUTING.md to solve these doubts from the beginning.

2- Add the new modules to Gradle. settings.gradle. Specify where that file is: /AnySoftKeyboard/settings.gradle

2- Rename the package names (com.anysoftkeyboard.english.* -> com.anysoftkeyboard.klingon.*:

• Specify that AndroidManifest.xml will be both on

  • /AnySoftKeyboard/addons/languages/klingon/apk/src/main/AndroidManifest.xml
    
    AND

  • /AnySoftKeyboard/addons/languages/klingon/pack/src/main/AndroidManifest.xml
    
    (Are those well? Do we have to change something else in those files?)

• Move the PackBroadcastReceiver package to the right place. Where is the right place?
  addons/languages/klingon/pack/src/main/java/com/anysoftkeyboard/languagepack/klingon/PackBroadcastReceiver.java?

4.3- Add text files that will be parsed - word-counted - to generate word-list XMLs.

• Where do we have to add those texts? Also in klingon/pack/dictionary/prebuilt? Or in klingon/pack/dictionary/inputs?
• What type of files are supported? .txt, .htm... also .html?

11- Edit the keyboard layouts. Explainations say that in android:codes must be used unicode values:

"android:codes" : a comma separated unicode values of the keys.

But in fact those are not unicode values, but HTML-codes. See both here: https://unicode-table.com/en/

12- Edit klingon_keyboards.xml.

• There are some parameters which point to @string/... but we're not able to find that directory (having copied the /addons/languages/english.)
• Is it mandatory to add physicalKeyboardMappingResId=?
• Should we add True in defaultEnabled= to the layout we want to be default? If we don't specify the others to False, will they be False anyway?

P.D.: I promise to complete the guide when I'll have all clear

[egils-consulting]

Could you add a compact Esperanto QWERTY variant?

[Porrumentzio]

Ĉu ekzistas iu, ekzemple en la angla pakaĵo, kiun vi ŝatas? Mi kredas ke mi povus uzi ĝin

[egils-consulting]

Jes tiun ĉi