Bug#401651: openoffice.org-writer: common hertz units get incorrectly modified due to two consecutive caps

[Michael Gilbert <michael.s.gilbert@gmail.com>]

Package: openoffice.org-writer
Version: 2.0.4-7
Severity: normal

entering MHz, GHz, THz, etc into oowriter will end up with Mhz, Ghz, and
Thz because these get incorrectly lumped into the two consecutive caps
checker.  please enter exceptions for units such as this.  or at least
do not correct these once they are entered into the dictionary as valid
words.

thank you for your consideration.

mike

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages openoffice.org-writer depends on:
ii  libc6                        2.3.6.ds1-8 GNU C Library: Shared libraries
ii  libgcc1                      1:4.1.1-19  GCC support library
ii  libicu36                     3.6-1       International Components for Unico
ii  libstdc++6                   4.1.1-19    The GNU Standard C++ Library v3
ii  libstlport4.6c2              4.6.2-3     STLport C++ class library
ii  libwpd8c2a                   0.8.7-4     Library for handling WordPerfect d
ii  openoffice.org-core          2.0.4-7     OpenOffice.org office suite archit
ii  python-uno                   2.0.4-7     Python interface for OpenOffice.or
ii  zlib1g                       1:1.2.3-13  compression library - runtime

Versions of packages openoffice.org-writer recommends:
ii  gij-4.1 [java2-runtime]     4.1.1-17     The GNU Java bytecode interpreter
ii  java-gcj-compat             1.0.65-8     Java runtime environment using GIJ
ii  openoffice.org-java-common  2.0.4-7      OpenOffice.org office suite Java s
ii  sun-java5-jre [java2-runtim 1.5.0-08-1.1 Sun Java(TM) Runtime Environment (

-- no debconf information