This repo holds all the official language packs for AnySoftKeyboard (in a mono-repo style).
Each language is a set of two modules, pack
and apk
. pack
is an Android library that holds all the information about the language pack (keyboards, dictionaries, receivers, etc.),
while apk
bundles that into an installable (and publishable) APK.
NOTE: this repo is in transition to mono-repo style. Some language-packs are in master while others are still in the old structure where each language-pack is a branch.
Let's say you want to create a language-pack for Klingon. We'll call the pack klingon
, and its locale is kl
.
- Easiest way to start, is to duplicate one of the other packs:
cp -R english klingon
. - Add the new modules to Gradle. Edit
settings.gradle
, add the line:
include ":languages:klingon:pack", ":languages:klingon:apk"
- At this point, you'll need to sync you Android Studio project.
- Rename the package names (
com.anysoftkeyboard.english.*
->com.anysoftkeyboard.klingon.*
:- Change
package
value inAndroidManifest.xml
files (one inpack
and the second inapk
). - Move the
PackBroadcastReceiver
package to the right place.
- Change
- Rename the
english_keyboards.xml
andenglish_dictionary.xml
files (underklingon/pack/src/main/res/xml
) toklingon_keyboards.xml
andklingon_dictionaries.xml
. - Replace the dictionary files under
klingon/pack/dictionary
with inputs matching your language (and remove what's not relevant):- Try to locate AOSP dictionary files (could be found at AOSP, or LineageOS) (you should use the
XX_wordlist.combined.gz
file). - If you have anything that was pre-built into a word-list XML, put those under
klingon/pack/dictionary/prebuilt
. - Add text files that will be parsed - word-counted - to generate word-list XMLs
- Try to locate AOSP dictionary files (could be found at AOSP, or LineageOS) (you should use the
- Generate the dictionary:
./gradlew :languages:kligon:pack:makeDictionary
. This will create the following files (which should not checked into the repo):- raw resources under
klingon/pack/src/main/res/raw/klingon_words_?.dict
- IDs resource array under
klingon/pack/src/main/res/values/klingon_words_dict_array.xml
- raw resources under
- Edit
klingon_dictionaries.xml
:- to point to the new array resource
@array/klingon_words_dict_array
- replace the
id
with a new GUID. - replace name and description
- replace the locale
- to point to the new array resource
- Set the status-bar icon text at
klingon/pack/build.gradle
:ext.status_icon_text = "kl"
- Replace the flag at klingon/apk/flag
with a, high-quality, png or svg, image of the flag. It should be named
flag.pngor
flag.svg`. Note that sometimes svg files are not converted correctly, but they will produce highest quality if successful. - To generate the icons, you'll need ImageMagick installed on your path. Check out the installation page for details.
- Generate the icons:
./gradlew :languages:kligon:pack:generateLanguagePackIcons :languages:kligon:apk:generateStoreLogoIcon
. This will generate the following files (which should be checked into the repo):klingon/pack/src/main/res/drawable-*/ic_status_kligon.png
klingon/apk/src/main/res/mipmap-*/ic_launcher.png
klingon/apk/src/main/play/listings/en-US/graphics/feature-graphic/pack_store_feature_graphics.png
klingon/apk/src/main/play/listings/en-US/graphics/icon/pack_store_icon.png
- Edit the keyboard layouts to your language, remove what's not needed, and add new ones if you need. Make sure the names of the layouts include you pack-name (klingon).
- Edit
klingon_keyboards.xml
. For each of the layouts you want in your pack (the layouts you created in the previous step):- Generate a new GUID.
- Set the locale value at
defaultDictionaryLocale
to match the value you used inklingon_dictionaries.xml
. - Set the status-bar icon at
iconResId
to the generate icon@drawable/ic_status_kl
- Update the texts (name and description).
At this point, you should be able to build an APK that can be installed on your device:
./gradlew :languages:klingon:apk:assembleDebug
or directly install it on your connected device:
./gradlew :languages:klingon:apk:installDebug
Iterate on your pack until you feel it is good, and then create a PR to merge it to the master.
You can either publish by yourself, under your developer account and keep complete ownership, or you can let us (aka AnySoftKeyboard organization) do it.
TO DO!!!
We have 13 language packs in this repo:
- Afrikaans_oss: Source • Play Store
- Armenian2: Source
- Brazilian: Source • Play Store
- English: Source
- French: Source • Play Store
- Greek: Source • Play Store
- Hebrew: Source • Play Store
- Indonesian: Source • Play Store
- Italian: Source • Play Store
- Romanian: Source • Play Store
- Russian2: Source • Play Store
- Spain: Source • Play Store
- Tamazight: Source • Play Store
Copyright 2018 Menny Even-Danan
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
This is the common template for language Packs for the AnySoftKeyboard app for Android devices. Each pack can contain and provide multiple keyboards or dictionaries for auto correction. Most packs are maintained here as branches of the repository and published to Google Play Store and F-Droid repository. There are some packs maintained as community forks, here on GitHub or not open source at all. Some of these are:
To start a new pack, follow this checklist:
-
Fork this repository.
-
Create a new branch, name it after the language.
-
In Android Studio, Refactor->Rename the folder/package com.anysoftkeyboard.languagepack.languagepack in the project tree, replacing the last
languagepack
with the name of the language. This will automatically change it at a couple of other locations. -
Change
applicationId
inbuild.gradle
in the same way. -
Edit
src/main/res/xml/keyboards.xml
according to the comments in it. It referencessrc/main/res/xml/qwerty.xml
, so edit this as well. Have a look at all the other Language Pack branches, to get an idea, what is possible and how to correctly configure a keyboard. -
If you want to add more keyboards, you can do this by copying
qwerty.xml
and add a element inkeyboards.xml
. The user can pre-select in the ASK settings, which keyboards she would like to have available for toggling through. -
Edit
src/main/res/xml/dictionaries.xml
-
Edit
src/main/res/values/strings.xml
, change the strings there and possibly add some more which are referenced in the other xml files. Also, create a new foldersrc/main/res/values-XX
, whereXX
is the correspondent two-letter ISO 639-1 language code. -
Edit (e.g. via Inkscape) one of the files in
src/main/svg-png/flag/
to represent the language, e.g. by using the flag from Wikipedia (the flag has to be placed on the right edge of the document and have the full height). -
Rebuild the drawables with
./gradlew svgToDrawablePng
or "Build" -> "Rebuild Project" in Android Studio. Drawables will be generated atsrc/main/res/mipmap-*/
. -
Choose whether you like the standard or the broad variant and set that as application's
android:icon
insrc/main/AndroidManifest.xml
. -
You can also add a new
src/main/res/drawable/flag.png
and reference it in theiconResId=""
attribute in the keyboards.xml. -
Put the source files for the dictionary into the dictionary/ directory. Take special care to take the conditions of the license into account, under which you obtained the data.
-
Change the build.gradle to use and configure the tasks necessary. There are several different variants (more Information):
GenerateWordsListTask
GenerateWordsListFromAOSPTask
MergeWordsListTask
-
Change the README.md to reflect the characteristics of your pack
-
Make some screenshots and replace the files in the
src/main/play/
folder. One of them should be a 1024x500 banner. -
If a branch of the language does not exist, open an issue to request the creation of a new branch. As soon, as it is created, you can make a Pull Request from your forked branch to the one in the original repository. Provide translations of the following strings to your language:
-
title: "LANGUAGE Language Pack"
-
promo: "LANGUAGE language pack for AnySoftKeyboard"
-
description: "AnySoftKeyboard keyboards pack: LANGUAGE keyboard and dictionary.
This is an expansion pack for AnySoftKeyboard. Install AnySoftKeyboard first, and then select the desired layout from AnySoftKeyboard's Settings->Keyboards menu."
When it is merged, it can take a couple of days, until it is also distributed via Play Store and F-Droid.
-