[porting-issues] [Issue 73103] No precomposed-character e ncodings in Windows installer strings

[sb]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73103


User sb changed the following:

What|Old value |New value

  Status|VERIFIED  |CLOSED





--- Additional comments from [EMAIL PROTECTED] Tue Mar 20 09:45:00 + 
2007 ---
.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[porting-issues] [Issue 73103] No precomposed-character e ncodings in Windows installer strings

[sb]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73103


User sb changed the following:

What|Old value |New value

  Status|RESOLVED  |VERIFIED





--- Additional comments from [EMAIL PROTECTED] Tue Jan 30 08:00:01 -0800 
2007 ---
.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[porting-issues] [Issue 73103] No precomposed-character e ncodings in Windows installer strings

[clytie]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73103





--- Additional comments from [EMAIL PROTECTED] Mon Jan 29 00:54:12 -0800 
2007 ---
Thanks. :)

That would help a lot.

Meanwhile, I need to get it built and tested. Do I ask Pavel for a build of 
that CWS?

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[porting-issues] [Issue 73103] No precomposed-character e ncodings in Windows installer strings

[sb]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73103





--- Additional comments from [EMAIL PROTECTED] Mon Jan 29 00:07:32 -0800 
2007 ---
@clytie:  That's the theory.  :)  You should verify it in practice, however.

But, just to be clear, note that this issue is not yet integrated.  It is on CWS
sb69 and is planned to be integrated into OOo 2.3 sometime soon.  If I don't
forget, I can post to this issue when it is integrated, so you can easily check.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[porting-issues] [Issue 73103] No precomposed-character e ncodings in Windows installer strings

[clytie]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73103





--- Additional comments from [EMAIL PROTECTED] Fri Jan 26 21:33:21 -0800 
2007 ---
Yay! :D

Does this mean I no longer need to run the conversion script over the .sdf file 
before submitting it?

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[porting-issues] [Issue 73103] No precomposed-character e ncodings in Windows installer strings

[sb]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73103


User sb changed the following:

What|Old value |New value

  Status|STARTED   |RESOLVED

  Resolution|  |FIXED





--- Additional comments from [EMAIL PROTECTED] Wed Jan 24 08:44:40 -0800 
2007 ---
Fixed.  All the Vietnamese-relevant precomposed Unicode characters that map to
MS1258 base + combining modifier, as derived from
, are now supported when mapping
from Unicode to MS1285.  In the opposite direction, MS1258 base + combining
modifier still map to Unicode base + Unicode combining modifier.  For example,
both Unicode

  U+1EF1 LATIN SMALL LETTER U WITH HORN AND DOT BELOW

and

  U+01B0 LATIN SMALL LETTER U WITH HORN, U+0323 COMBINING DOT BELOW

map to MS1258

  0xFD 0xF2

and that maps back exclusively to

  U+01B0 LATIN SMALL LETTER U WITH HORN, U+0323 COMBINING DOT BELOW.

(I hope I got those mapping tables right, they have effectively been
handcrafted.)  For testing, see sal/qa/rtl/textenc/rtl_textcvt.cxx:1.9.34.1.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[porting-issues] [Issue 73103] No precomposed-character e ncodings in Windows installer strings

[clytie]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73103





--- Additional comments from [EMAIL PROTECTED] Sun Jan  7 20:18:37 -0800 
2007 ---
The important thing is that it works. If there are decomposed-display problems 
with some systems, 
we'll handle them then. The majority result, possibly the complete result, will 
be a solution for the 
persistent lack of Unicode support in NSIS, which has caused these scrambled 
Windows installer screens 
for so many languages, in different translation projects.

See http://www.openoffice.org/issues/show_bug.cgi?id=73192 for the workaround 
conversion script.

Thankyou to pavel, sb and timar for their help with this problem, which was 
blocking our Windows 
release.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[porting-issues] [Issue 73103] No precomposed-character e ncodings in Windows installer strings

[clytie]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73103





--- Additional comments from [EMAIL PROTECTED] Fri Jan  5 20:40:13 -0800 
2007 ---
pjanik: I set P2 because it's stopping people installing OpenOffice.org. They 
can't understand the first 
screens and just trash the app. :(

sb: it's a possible workaround, but the problem is that decomposed Unicode is 
not uniformly supported. 
Different software (app or system) will handle it differently, resulting in 
displays which separate the base 
character and diacritic, and even, in one fascinating case, where diacritics 
became separated from the 
parent vowel and followed the cursor around the page. I spent several months 
once debugging a 
multiple and severe input/display problem that turned out to be caused by the 
use of decomposed 
Unicode, so I avoid it strictly since then.

I'll consult on this. If we do decide decomposed Unicode is a worthwhile 
temporary option, how do we 
identify these strings in the overall GSI file? The last thing we want is the 
whole UI in decomposed 
characters.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[porting-issues] [Issue 73103] No precomposed-character e ncodings in Windows installer strings

[sb]

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=73103


User sb changed the following:

What|Old value |New value

   Component|l10n  |porting

  Status|NEW   |STARTED

  OS/Version|Windows XP|All

  QA contact|[EMAIL PROTECTED]   |[EMAIL PROTECTED]

Target milestone|---   |OOo 2.3





--- Additional comments from [EMAIL PROTECTED] Thu Jan  4 02:41:10 -0800 
2007 ---
As discussed in issue 72905, this is a problem of the sal/textenc functionality
that translates from Unicode to MS 1258.

@clytie:  As a work around for the moment, it might work if you decompose the
problematic precomposed Unicode characters (like U+1ECB LATIN SMALL LETTER I
WITH DOT BELOW to U+0069 LATIN SMALL LETTER I U+0323 COMBINING DOT BELOW) in the
Unicode text that is translated to MS 1258.  (If that does not cause problems
with displaying the Unicode text on other platforms, where it is not translated
to MS 1258.)

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]