Specific rules need to be executed in certain order. Wrap the
UNPACK_RULES to a list, so the order of the rules can be specified.

Change-Id: Ib160a814b49ed25fd0ed85337cfddf80afa0ccd7
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

[ChangeLog] Added Hebrew keyboard layout.

Change-Id: I7779db4e5ac3c5a99937a0d7b7e572db65f0d811
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

[ChangeLog] Added Arabic handwriting.

Change-Id: Ica0601da2df262369159415d28fdb183e6f63736
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

The commit bc84550e

 added an option
to unpack a directory. However, the feature was not compatible with
python 3 due to incorrect chmod parameter. This change fixes the
parameter so it works with python 2 and 3.

Change-Id: Iaf74f2be660d6ee5de6cd58cc9c983707b2a9364
Reviewed-by: Liang Qi <liang.qi@qt.io>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

This change allows the rules with same input file name (but
with different directory prefix) to co-exist. It works by
removing the already matched input file from the "zip list".
However, this only works if the rules are ordered correctly,
i.e. the most exact ones being first in the list.

Consider the following example:

'data/arabic': [
    '*/Arabic/_databas_le.bin',
],
'data': [
    '*/_databas_le.bin',
]

Without this change the later rule will override the
file entry already copied for 'data/arabic'. But with
'Arabic/_databas_le.bin' removed from the input list, it
will not be matched.

Change-Id: Ifd06125d1519c45dba077e50f69769fdb0070351
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Accept directory as an input argument in addition to zip file.

Change-Id: I2faf446f7636d190941fae0f76e569cb1e7c332e
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

QStringLiteral is broken in MSVC2015 onwards when used with \uXXXX
encoded character literals. This was the reason Japanese tests were
failing - the OpenWNN engine was actually broken and producing
garbage.

Not only this change eliminates QStringLiteral from openwnn, but also
reduces runtime memory usage by replacing QMap<QString, QString>.

The new solution is based on simple binary lookup table WnnLookupTable.
WnnLookupTable data was converted from existing QMap structures using
WnnLookupTable::create() method, which was left there for future
reference.

This change also removes the unnecessary QObjectPrivate definitions
from Romkan* classes.

[ChangeLog][OpenWNN] Fixed and optimized OpenWNN engine (as a workaround
for QStringLiteral breakage)

Task-number: QTBUG-62133
Change-Id: I50c9e2f5c363e1314f47d7023685da543ec9a7eb
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
(cherry picked from commit 0bf1c6ad)

Reduces allocations.

This is the result of running the (experimental) clang-tidy check
   qt-modernize-qsharedpointer-create

Discarded changes: none.

Change-Id: I9ef1ccd46315f1bb8f3cc30a652f17c18b46232c
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

This change adds support for handwriting in Simplified Chinese.

The integration is based on T9 Write CJK SDK v7.8.1.

[ChangeLog] Added support for CJK (Chinese/Japanese/Korean) handwriting
via T9 Write.

Change-Id: I18481cfd897987ecb471c49ecfcac62ea0c3489c
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Liang Qi <liang.qi@qt.io>

QStringLiteral is broken in MSVC2015 onwards when used with \uXXXX
encoded character literals. This was the reason Japanese tests were
failing - the OpenWNN engine was actually broken and producing
garbage.

Not only this change eliminates QStringLiteral from openwnn, but also
reduces runtime memory usage by replacing QMap<QString, QString>.

The new solution is based on simple binary lookup table WnnLookupTable.
WnnLookupTable data was converted from existing QMap structures using
WnnLookupTable::create() method, which was left there for future
reference.

This change also removes the unnecessary QObjectPrivate definitions
from Romkan* classes.

[ChangeLog][OpenWNN] Fixed and optimized OpenWNN engine (as a workaround
for QStringLiteral breakage)

Change-Id: I50c9e2f5c363e1314f47d7023685da543ec9a7eb
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Change-Id: Ib358606c36a668f4d8a0c03db756f894dac0b872
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

warning: LNK4044: unrecognized option '/pthread'; ignored

Change-Id: I76425aa3449e6e186f2bae9b0e62ede3fda14420
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Lipi-toolkit projects were not deployed in non-prefix builds.

The suspected cause is COPIES directive being ignored in AUX project.

Moved deployment to virtualkeyboard.pro as workaround. This is also
consistent with other deployments.

Change-Id: I82237c1e1e6ee9b001294ff3b22fb5cd013b8105
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
Reviewed-by: Jarkko Koivikko <jarkko.koivikko@code-q.fi>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

fa5cd9cc

 change the format of the
Hunspell header includes, but it was the MODULE_INCLUDEPATH that
was wrong, so fix that instead. The previous (incorrect) value was:

MODULE_INCLUDEPATH = $$PWD/src/hunspell

when it should be:

MODULE_INCLUDEPATH = $$PWD/src

Change-Id: Ifa5b13a9cede3ccc9712cca03c17cb2fdae56134
Reviewed-by: Jarkko Koivikko <jarkko.koivikko@code-q.fi>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

This was causing compiler errors about a missing <hunspell/hunspell.h>

Change-Id: Ia7d8360026bf3105ff5b1828b0c7365730cb15a4
Reviewed-by: Jarkko Koivikko <jarkko.koivikko@code-q.fi>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

qtt9write_db library was not generated due to missing QT=core.

Change-Id: I4005008b72ac55023f6c78158d1b6464fdec3a40
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

- dictmgr.hxx and dictmgr.cxx files were removed from hunspell
- Some files were complaining about a missing <hunspell/hunspell.h>
  include. Changing it to <hunspell.h> fixed it.

Task-number: QTBUG-57415
Change-Id: Ib2331bf28b3f60370730ca3534469e463d062dee
Reviewed-by: Jarkko Koivikko <jarkko.koivikko@code-q.fi>
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

qtConfig() is new in 5.8.

amends cdd7df86

.

Task-number: QTBUG-56072
Change-Id: Ibea8d460165dd2e4eafe366105482ce93078ccc3
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Jake Petroules <jake.petroules@qt.io>

our lipi build system doesn't use any of the usual prfs, so it needs to
deal with dual builds itself.

Task-number: QTBUG-56072
Change-Id: Ife44fb4b29c0f55228b97579f4a4d9317e75f0aa
Reviewed-by: Jake Petroules <jake.petroules@qt.io>

Change-Id: I19b606ce91bad3f92112932688db16b39e9190ed
Reviewed-by: Topi Reiniö <topi.reinio@theqtcompany.com>

Change-Id: Ibde3fa65b4c3d967fe9ada1b5e484366f1e9d083
Reviewed-by: Jake Petroules <jake.petroules@qt.io>

Installing plugins into a data path is a very bad idea, even more so
when the path disagrees with the non-prefix location.

The default LIPI_ROOT contains both the plugins and the projects needed
at runtime for handwriting recognition. This change adds new environment
variable LIPI_LIB which points to location for plugins only. This allows
the separation of the two.

Change-Id: Ie50b6871b6d176b2d06ff068743b40e9daa2c5cb
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>

Task-number: QTBUG-52256
Change-Id: I1efc42c6d65516beedacc1d262bac2531f047a67
Reviewed-by: Liang Qi <liang.qi@qt.io>

This change fixes the lipi-toolkit build since commit
e2b650f2



Change-Id: I85e02e632020bcff577f1d42b412f7f98b023e3c
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>

CROSS_COMPILE is not reliable way to determine if ARM files should be used.

Change-Id: Ie15f823da822776836dee61bc54df3e4a5aaabd2
Reviewed-by: Kalle Viironen <kalle.viironen@theqtcompany.com>
Reviewed-by: Andy Nichols <andy.nichols@qt.io>

Static build requires HUNSPELL_STATIC for correct linkage.

Change-Id: I5ed7b1c40d7f3a4af82d997acdcda6f6d785f745
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Change-Id: Ica7c278e9cee0af5dab86dd7fb1e092df420fc54
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

linux distributors don't like it at all when arch-specific binaries
end up in shared data directories.

Change-Id: I2f983cb8fc3713fea25cd103013d0ce5356ffa0c
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>

this ensures naming and installation uniformity.

hunspell is now built statically, for the same reason.

Change-Id: I722f16bda4671a71419920f3ab3bedf03df92f0e
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>

Change-Id: Id31e400061baae6f91f3a670e85058276d23f857
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>

it doesn't really make sense to have a dummy project for headers.

Change-Id: I1686ddfaeca7e62a15d861935a521c4ddbb939a6
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>

it's counterproductive to separate the member definitions from the
object reference.

Change-Id: I4fed5cf5e84f4a2ee6f79482a18937d712f4e62d
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>

use project names instead of the generated makefile targets.

Change-Id: I024da821ecb012d653065b130431d5aedcf15341
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>

Change-Id: I494c31c698db1d6c03dbec65105fcd5254c8b4f9
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>

This change modifies the files that exist in the 2.0 version.

Fix static build of the virtual keyboard:
- Disable static build for lipi toolkit (as the architecture
  does not support static build).

Change-Id: Iea73af647ffd10a6e5aedc12bd1e1b4e38d26827
Reviewed-by: Rainer Keller <rainer.keller@theqtcompany.com>
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>

Add new configuration flags to simplify the customization process
of the virtual keyboard.

- lang-<code> flag enables the specified language.
- lang-all flag enables all the languages.
- handwriting flag enables the handwriting input method (t9write
  or lipi-toolkit)

Updated test cases and also fixed the virtual keyboard for single
language support.

Change-Id: I599816bed591bd193ad26cef0e9bf4812146e865
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>

Zhuyin can be enabled with CONFIG+=tcime or CONFIG+=zhuyin qmake flags.
Note that CONFIG+=tcime enables both Cangjie and Zhuyin input methods.
You can also enable the Cangjie input method with CONFIG+=cangjie,
in which case the Zhuyin input method will not be activated, unless
the config contains CONFIG+=zhuyin also.

Change-Id: Iddea01f3e3d7f1dafff80e17da5b7cf89d4cfc55
Task-number: QTRD-3726
Reviewed-by: Rainer Keller <rainer.keller@theqtcompany.com>
Reviewed-by: Liang Qi <liang.qi@theqtcompany.com>

This change adds Cangjie input method for Traditional Chinese.

The input method is based on the TCIME input method for Android.

https://code.google.com/p/android-traditional-chinese-ime/



The Cangjie input method is enabled by adding CONFIG+=tcime into
qmake command line.

The version of the Cangjie input is v3.

Change-Id: Ibc49484d1277c332fc17e9b49b4227256ad88d5a
Reviewed-by: Liang Qi <liang.qi@theqtcompany.com>
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>
Reviewed-by: Rainer Keller <rainer.keller@theqtcompany.com>

This change adds T9Write implementation of HandwritingInputMethod.

To use the T9Write, the contents of T9Write sdk must be extracted
to srv/virtualkeyboard/3rdparty/t9write directory and the qmake
command line must contain CONFIG+=t9write.

Change-Id: Ib56d1d3dc553bb5d5677ab03e213dc8fed43ac68
Reviewed-by: Mitch Curtis <mitch.curtis@theqtcompany.com>

This also allows it to build both debug and release on Windows when
debug_and_release is set by enabling build_all.

This change modifies the project files which exist in 2.0 version.

Task-number: QTBUG-47255
Change-Id: Ie03530bbc19b16ed5916bb2190e9b4139fde0a3f
Reviewed-by: Andy Shaw <andy.shaw@theqtcompany.com>