diff options
author | hbono@chromium.org <hbono@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-10-24 02:33:22 +0000 |
---|---|---|
committer | hbono@chromium.org <hbono@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-10-24 02:33:22 +0000 |
commit | 361504f357e6882891f56aaf84dfa521a87f8739 (patch) | |
tree | eec77fc4990d6b183833117abb407eacf5ea88ef /chrome/browser/rlz/rlz.cc | |
parent | 3453068e7facd042b827a011a56ee516409fa07b (diff) | |
download | chromium_src-361504f357e6882891f56aaf84dfa521a87f8739.zip chromium_src-361504f357e6882891f56aaf84dfa521a87f8739.tar.gz chromium_src-361504f357e6882891f56aaf84dfa521a87f8739.tar.bz2 |
Fix Issue 1356872 "Russian bdic is corrupted".
The AffReader::AddAffix() function does not reencode a "stripping prefix (or
suffix)" field of a PFX (or SFX) line.
Unfortunately, this function creates corrupted prefix (and suffix) rules for
some dictionaries whose encoding is not UTF-8 (e.g. Russian, Polish, etc.)
because a "stripping prefix (or suffix)" field isn't only a length of a prefix
(or suffix) but also it is a string to be replaced.
To solve this problem, this change branch checks the third token of an PFX (and
SFX) line represents a "stripping characters" field or a "cross product" field,
and reencode them only if the third token represents a suffix or a prefix.
Needless to say, we also have to re-create bdics and push them to our download
server to solve this issue. :)
BUG=1428
Review URL: http://codereview.chromium.org/3183
Review URL: http://codereview.chromium.org/3183
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@3903 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/rlz/rlz.cc')
0 files changed, 0 insertions, 0 deletions