### File header must not be modified | |
### This file must be encoded into UTF-8. | |
### This table under LGPL | |
### comments start with ### not single # | |
### Derive from the format of SCIM Table, so you can modify the table from | |
### scim-tables' table | |
SCIM_Generic_Table_Phrase_Library_TEXT | |
VERSION_1_0 | |
### Begin Table definition. | |
BEGIN_DEFINITION | |
### License | |
LICENSE = LGPL | |
### An unique id to distinguish this table among others. | |
### Use uuidgen to generate this kind of id. | |
UUID = e26be2ff-1064-4d70-98c4-f440d686cbc1 | |
### A unique number indicates the version of this file. | |
### For example the last modified date of this file. | |
### This number must be less than 2^32. | |
### Just make your table version-able | |
SERIAL_NUMBER = 20160512 | |
### ICON can be any format as long as your pygtk can recognized | |
### the most widely ones are "png" and "svg", letter one is recommended | |
ICON = hy-phonetic.svg | |
### The symbol to be displayed in IM switchers | |
SYMBOL = Հ | |
### The default name of this table, this is needed | |
NAME = Table | |
### The local names of this table, this is optional | |
### NAME.zh_CN = 形码 | |
### NAME.zh_HK = 形碼 | |
### NAME.zh_TW = 形碼 | |
### Description | |
DESCRIPTION = Armenian phonetic layout for IBus Table. | |
### Supported languages of this table | |
### sigle "zh_CN" just be recognized as zh_CN, | |
### but "zh_CN, zh_HK" or more zh_XX will be recognized as zh; | |
### and "en_US, zh_CN" will be just ignored. | |
LANGUAGES = hy_AM | |
### The author of this table | |
AUTHOR = Nikita <mail@mail.com> | |
### Prompt string to be displayed in the status area, CN will be replaced by | |
### the gettext tools in runtime as 中. | |
STATUS_PROMPT = HY | |
### Valid input chars. | |
VALID_INPUT_CHARS == abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ`1234567890-=~!@#$%^&*()_+[]\{}|;':",./<>? | |
### Layout | |
LAYOUT = us | |
### The max number of input keys for every phrase or character. | |
MAX_KEY_LENGTH = 1 | |
### Use auto_commit mode as default | |
AUTO_COMMIT = TRUE | |
### Automatically selects the first phrase when typing | |
AUTO_SELECT = FALSE | |
### Use full width punctuation by default | |
DEF_FULL_WIDTH_PUNCT = FALSE | |
### Not use full width letter by default | |
DEF_FULL_WIDTH_LETTER = FALSE | |
### Whether user are allow to define phrase, default is true | |
### You have to define the word construction rules below. | |
### For input methods which do not input phrases, set this to False | |
USER_CAN_DEFINE_PHRASE = FALSE | |
### Whether support PinYin Mode, default is true. | |
### this feature is just for Chinese, set it to False if your IM is not | |
### Chinese. | |
PINYIN_MODE = FALSE | |
### If true then the phrases' frequencies will be adjusted dynamically | |
### according your using frequency. | |
DYNAMIC_ADJUST = FALSE | |
### Some characters whose frequencies should be fix all the time, e.g. | |
### some punctuations | |
### NO_CHECK_CHARS = | |
### Rules for constructing user defined phrase | |
### "ce" stands for "ci equal", a Chinese English :), means "phrase length | |
### equal to", thus ce2 -> phrase length equal to 2; and "ca" means "phrase | |
### length equal or above", so ca4 -> phrase length equal or above 4. | |
### p21 -> the 1st key of 2nd character in the phrase, and so on. | |
### Each rule separate via ";". | |
### Example below is a complete rule-set, | |
### becuase [2,2] ∩ [3,3] ∩ [4,+∞] = [2,+∞], which is the range of length | |
### of phrase. This have to be satisfied if you need ibus-table to build up | |
### your own inputed phrase via your daily using. | |
### RULES = ce2:p11+p12+p21+p22;ce3:p11+p21+p22+p31;ca4:p11+p21+p31+p41 | |
### The key strokes to page up the lookup table. | |
### PAGE_UP_KEYS = Page_Up,KP_Page_Up,minus,comma | |
### The key strokes to page down. | |
### PAGE_DOWN_KEYS = Page_Down,KP_Page_Down,equal,period | |
END_DEFINITION | |
### Begin Table data. | |
### Format of every line whose formated in "input_keys\tphrase\tfreq\n" is an | |
### entry. | |
### From left to right, the 1st column are the input key combination that you | |
### entered via keyboard; the 2nd column are presented character or phrase of | |
### the key combination you want; the 3rd column are frequency of the character | |
### or phrase. | |
BEGIN_TABLE | |
` ՝ 1 | |
1 է 1 | |
2 թ 1 | |
3 փ 1 | |
4 ձ 1 | |
5 ջ 1 | |
6 ւ 1 | |
7 և 1 | |
8 ր 1 | |
9 չ 1 | |
0 ճ 1 | |
- ֊ 1 | |
= ժ 1 | |
~ ՜ 1 | |
! Է 1 | |
@ Թ 1 | |
# Փ 1 | |
$ Ձ 1 | |
% Ջ 1 | |
^ Ւ 1 | |
& և 1 | |
* Ր 1 | |
( Չ 1 | |
) Ճ 1 | |
_ ― 1 | |
+ Ժ 1 | |
q ք 1 | |
w ո 1 | |
e ե 1 | |
r ռ 1 | |
t տ 1 | |
y ը 1 | |
u ւ 1 | |
i ի 1 | |
o օ 1 | |
p պ 1 | |
[ խ 1 | |
] ծ 1 | |
\ շ 1 | |
Q Ք 1 | |
W Ո 1 | |
E Ե 1 | |
R Ռ 1 | |
T Տ 1 | |
Y Ը 1 | |
U Ւ 1 | |
I Ի 1 | |
O Օ 1 | |
P Պ 1 | |
{ Խ 1 | |
} Ծ 1 | |
| Շ 1 | |
a ա 1 | |
s ս 1 | |
d դ 1 | |
f ֆ 1 | |
g գ 1 | |
h հ 1 | |
j յ 1 | |
k կ 1 | |
l լ 1 | |
; ; 1 | |
' ՛ 1 | |
A Ա 1 | |
S Ս 1 | |
D Դ 1 | |
F Ֆ 1 | |
G Գ 1 | |
H Հ 1 | |
J Յ 1 | |
K Կ 1 | |
L Լ 1 | |
: ։ 1 | |
“ “ 1 | |
z զ 1 | |
x ղ 1 | |
c ց 1 | |
v վ 1 | |
b բ 1 | |
n ն 1 | |
m մ 1 | |
, , 1 | |
. ․ 1 | |
/ / 1 | |
Z Զ 1 | |
X Ղ 1 | |
C Ց 1 | |
V Վ 1 | |
B Բ 1 | |
N Ն 1 | |
M Մ 1 | |
< « 1 | |
> » 1 | |
? ՞ 1 | |
END_TABlE | |
### Since some input methods use different table for every character to make | |
### phrase, such as ZhengMa, they need explict define the goucima (the | |
### phrase-building code for the given character), the format of every entry is | |
### "character\tgoucima\n". | |
### For the input method which just use the full code as word-building code | |
### just skip this field. The ibus-table will build the codes needed from | |
### above TABLE. | |
### if you don't need different word-building code, please comment out the | |
### next few lines with ###, just like these lines you are look at now. | |
BEGIN_GOUCI | |
character_1 goucima_1 | |
character_1 goucima_2 | |
END_GOUCI |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment