Bug 480871 - I18N - After exporting Definition i18n chars change to garbage
Summary: I18N - After exporting Definition i18n chars change to garbage
Status: VERIFIED INVALID
Alias: None
Product: Vibe
Classification: Micro Focus Vibe
Component: Administration (show other bugs)
Version: 2.0.0
Hardware: x86 Windows XP
: P2 - High : Normal
Target Milestone: 2.0.0
Assignee: Roy Klein
QA Contact: Forgotten User vd_J2WSqeK
URL:
Whiteboard:
Keywords: Built, CCB, I18N
Depends on:
Blocks:
 
Reported: 2009-03-02 08:52 UTC by Rose Tian
Modified: 2015-02-03 07:21 UTC (History)
2 users (show)

See Also:
Found By: i18n Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Rose_20090302_ExportDefinition_1.jpg (50.57 KB, image/pjpeg)
2009-03-02 08:52 UTC, Rose Tian 		Details
rose_20090316_ExportDefinition_2.jpg (74.46 KB, image/jpeg)
2009-03-16 02:06 UTC, Rose Tian 		Details
rose_20090316_TestData.txt (152 bytes, text/plain)
2009-03-16 02:15 UTC, Rose Tian 		Details
rose_20090316_ExportDefinition_2.jpg (74.46 KB, image/jpeg)
2009-03-16 02:20 UTC, Rose Tian 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rose Tian 2009-03-02 08:52:52 UTC 
Created attachment 276306 [details]
Rose_20090302_ExportDefinition_1.jpg

Environment:
Server: sles10sp2 + installer-teaming-20090215030037.linux
Client: windows xp sp3 (DEU) + IE7 

Pre-Step: 

Steps to Reproduce:
1. Login Teaming (http://TeamingServer:8080) with admin user
2. Go to Manage-->Form and View Designers
3. Click New-->Entry Definitions,enter Caption and name with i18n chars
   (e.g. äößÜ-German)
4. Click the created Entry Definition,then Export This Definition
5. Save the definitions.zip to locale,and open it

Actual Results:
  xml file name displayed as garbage chars
  Pls see the screen shot Rose_20090302_ExportDefinition_1.jpg

Expected Results:
  xml file name with i18n chars should be displayed well

Notes:
  In step3,creating other definitions have the same issue.
Comment 1 Forgotten User btYcul-f_O 2009-03-02 22:34:17 UTC 
It sounds like the code that creates the xml file is not using utf-8.

Janet wrote all of this. Can you fix it? or pass it along to someone else?
Comment 2 Roy Klein 2009-03-03 23:31:40 UTC 
Fixed by changing the default encoding to cp437 when exporting to a zip file.
Comment 3 Rose Tian 2009-03-10 09:00:05 UTC 
Hi,which build will this issue be fixed?Thanks!
Comment 4 Roy Klein 2009-03-10 14:48:10 UTC 
I checked in the change on 3/3/09, you should see the fix in any build after that date.
Comment 5 Rose Tian 2009-03-12 08:54:08 UTC 
On the build 10682,this issue still can be reproduced,the xml file name display as question mark.
Comment 6 Rose Tian 2009-03-12 08:55:22 UTC 
On the build 10682,this issue still can be reproduced,the xml file name display
as question mark
Comment 7 Roy Klein 2009-03-13 14:32:38 UTC 
I just tried it on our production system - aspendemo.sitescape.com and it works as expected.  Before I checked in the fix for this, I was able to reproduce it exactly as documented.  Now, I cannot reproduce it.
Comment 8 Rose Tian 2009-03-16 01:56:36 UTC 
Now,on German OS the German chars can be displayed well,if the name contains other i18n chars(e.g.※₢¤£סֶאבױﻯﻰﻱﻲﻳﻴﻻﻼกญกั๓亜営㈔㈲鳌齄㐀㐁㐂㐃ꀀꀁꀂꀃꀄꀅꀆꀇ嗀﨎ÆÇÎÛæøêïäößÜΓΔЖ),some chars displayed as question mark.Pls see the screen shot rose_20090316_ExportDefinition_2.jpg
Comment 9 Rose Tian 2009-03-16 02:06:52 UTC 
Created attachment 279666 [details]
rose_20090316_ExportDefinition_2.jpg
Comment 10 Rose Tian 2009-03-16 02:15:43 UTC 
Created attachment 279670 [details]
rose_20090316_TestData.txt

Test Data
Comment 11 Rose Tian 2009-03-16 02:20:06 UTC 
Created attachment 279671 [details]
rose_20090316_ExportDefinition_2.jpg
Comment 13 Tom Urquhart 2009-06-23 20:41:36 UTC 
ccb:  Java 7 not supported for Boulder.