Issue 49076 - on freebsd-4, in filter/source/... , java merger program corrupts UTF-8 strings
Summary: on freebsd-4, in filter/source/... , java merger program corrupts UTF-8 strings
Status: CLOSED DUPLICATE of issue 47000
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: 680m95
Hardware: PC FreeBSD
: P3 Trivial (vote)
Target Milestone: ---
Assignee: yury_t
QA Contact: issues@tools
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2005-05-11 09:10 UTC by yury_t
Modified: 2008-05-17 23:47 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description yury_t 2005-05-11 09:10:39 UTC 
Happens when building on freebsd-4 with port of Sun java-1.4.2.

When processing in filter/source/config/fragments, java merger program(when with 
-debug parameter, set in makefiles by default) uses UTF-8Special encoding, which 
leads to corruption of UTF-8 strings read from localize.sdf files. Alternative 
python script works okay and the merger works okay, too, if hacked to get rid of 
this encoding (non-existing on this platform+runtime combination perhaps?). I 
couldn't find the definite place of unsetting the option in makefiles.

The fragment in question is this:

--- ooo_SRC680_m95_src/filter/source/config/tools/merge/Merger.java.prev        
Tue Mar 22 07:35:25 2005
+++ ooo_SRC680_m95_src/filter/source/config/tools/merge/Merger.java     Fri Apr 
29 17:56:55 2005
@@ -352,7 +352,7 @@
         boolean bDebug               = m_aCfg.getBoolean(PROP_DEBUG       , 
false);
         java.lang.String sEncoding   = "UTF-8";
         if (bDebug)
-            sEncoding = "UTF-8Special";
+            sEncoding = "UTF-8"; //"UTF-8Special";

         while(pFragments.hasMoreElements())
         {
Comment 1 pavel 2005-05-11 12:29:55 UTC 
This is duplicate of 47000 and its followups.
Comment 2 pavel 2005-05-11 12:30:57 UTC 
duplicate

*** This issue has been marked as a duplicate of 47000 ***
Comment 3 ace_dent 2008-05-17 21:42:40 UTC 
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 4 ace_dent 2008-05-17 23:47:25 UTC 
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew