Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0009602Openbravo ERPY. DBSourceManagerpublic2009-06-24 09:442009-06-25 00:00
networkb 
marvintm 
immediatemajoralways
closedunable to reproduce 
30
2.40MP3 
 
Core
No
0009602: The xml files generated when exporting the database are not exported as utf-8 in windows
The xml files generated when exporting the database are not exported as utf-8 in windows
-In a windows XP machine execute ant export.database
-See that the files are not exported to utf-8
reviste the exporting process to ensure that the outputs are defined with utf-8

something similar was done in
https://issues.openbravo.com/view.php?id=9302 [^]
No tags attached.
related to defect 0009302 closed alostale The xml files created when a language is exported are not generated with utf-8 enconding when using window 
depends on backport 0009603 closed marvintm The xml files generated when exporting the database are not exported as utf-8 in windows 
Issue History
2009-06-24 09:44networkbNew Issue
2009-06-24 09:44networkbAssigned To => marvintm
2009-06-24 09:51rafarodaRelationship addedrelated to 0009302
2009-06-24 09:51rafarodaStatusnew => scheduled
2009-06-24 09:51rafarodafix_in_branch => pi
2009-06-24 17:25marvintmStatusscheduled => closed
2009-06-24 17:25marvintmNote Added: 0017567
2009-06-24 17:25marvintmResolutionopen => unable to reproduce
2009-06-25 00:00anonymoussf_bug_id0 => 2811788

Notes
(0017567)
marvintm   
2009-06-24 17:25   
This issue couldn't be reproduced (tried with Windows XP+Oracle, and the XML files were fine).

Chances are that the cause of this problem is not an incorrect behaviour of export.database, but instead the database encoding for the Oracle instance.

When an Oracle instance is created, you need to specify the database encoding. In Linux, the default encoding is UTF-8, but in Windows, it's not, and you need to remember to specify it, because if you don't, the Oracle database will be incorrectly created, and this will be a problem for Openbravo.