User-Agent: Mozilla/5.0 (X11; U; Linux i686; cs-CZ; rv:184.108.40.206) Gecko/20081030 SeaMonkey/1.1.13 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; cs-CZ; rv:220.127.116.11) Gecko/20081030 SeaMonkey/1.1.13 Typing the letters "ů" and "Ů" on my keyboard (it is defined by prefix "SHIFT"+"=/+" followed by u or U) nothing appeared - it concerns to various (probably all) components: mail, composer, browser, address book. The same problem appeared in Mozilla 1.7.5 and was solved in Mozilla 1.7.12. I use ISO-8859-2 encoding where the numbers of these characters are 217 and 249 (D9 and F9 hexadecimally). Reproducible: Always Steps to Reproduce: 1. Open e.g. a mail window. 2. Try to write the character 217 or 249 in the ISO-8859-2 encoding.
Josef, this could have been fixed in Gecko 1.9.1 (it's most likely a back-end issue). Would you mind trying a trunk build and see if the problem has gone? You can find linux trunk builds here: http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ Note that this builds are of alpha-quality... They shouldn't do any harm to your existing profile, but you'll be asked if you want to migrate profiles/data at startup (if you choose to do that the old profile will be copied to a new location, then used).
(In reply to comment #0) > The same problem appeared in Mozilla 1.7.5 and was solved in Mozilla 1.7.12. It would be interesting to know which bug that was. Does it happen with Firefox v2.0/v3.x too ?
Version: unspecified → SeaMonkey 1.1 Branch
(In reply to comment #2) > (In reply to comment #0) > > The same problem appeared in Mozilla 1.7.5 and was solved in Mozilla 1.7.12. > > It would be interesting to know which bug that was. I made a mistake - it was not exactly the same problem, but analogous with the letter "ó" (instead of it "ń" was written). The bug report is 258267 - there was no response to it but was somehow solved. > Does it happen with Firefox v2.0/v3.x too ? I tested Firefox 18.104.22.168 and 22.214.171.124 and there is the same problem.
OK, thanks. Hmm, bug 258267 was resolved as expired, so we can't be sure that this is a regression. It'd still be interesting to know if this happens with Firefox 3.x or a seamonkey trunk build.
I'm not have this problem in Windows XP SP3 (SeaMonkey 1.1.3 and SeaMonkey 2.0a2pre)
(In reply to comment #4) > OK, thanks. Hmm, bug 258267 was resolved as expired, so we can't be sure that > this is a regression. It'd still be interesting to know if this happens with > Firefox 3.x or a seamonkey trunk build. Yes, the same problem is in Firefox 3.0.4 and SeaMonkey 2.0a3pre - tested in 2.6.23-gentoo-r9.
A colleague tested this problem on another computer (2.6.23-gentoo-r9) with a different keyboard definition with the following results: * The same problems appears if the two letters are given using a prefix. * His keyboard definition allows to write the letter "ů" directly - in this case the problem does not appear. There does not seem to be a problem with other letters typed using a prefix.
Hmm, does bug 178721 looks related?
Assignee: nobody → smontagu
Component: General → Internationalization
Product: SeaMonkey → Core
QA Contact: general → i18n
Version: SeaMonkey 1.1 Branch → Trunk
(In reply to comment #8) > Hmm, does bug 178721 looks related? Hard to tell - bug 178721 comment #0 seems to have been garbled by not-yet-Unicode Bugzilla in 2002. OTOH, bug 178721 comment #7 may help (or not, see bug 178721 comment #8).
FWIW, on my fr_BE keyboard, all six dead keys (circumflex, umlaut, acute, grave, tilde and even breve = AltGr+Shift+µ) produce the desired results -- but my locale encoding is not ISO-8859-2 but (I think) UTF-8.
You need to log in before you can comment on or make changes to this bug.