Issue 57224 - CWS thaiissues doesn't start when OOo install path contains Thai chars
Summary: CWS thaiissues doesn't start when OOo install path contains Thai chars
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 680m137
Hardware: PC Windows XP
: P2 Trivial (vote)
Target Milestone: OOo 2.0.1
Assignee: hennes.rohling
QA Contact: issues@framework
Depends on:
Blocks: 41707
  Show dependency tree
Reported: 2005-11-02 17:29 UTC by eric.savary
Modified: 2006-02-09 09:46 UTC (History)
1 user (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description eric.savary 2005-11-02 17:29:03 UTC
Win XP with complex script installed and locales to Thai
- install CWS thaissues in path containing Thai characters
- Start the CWS
-> Message "missing VCL ressources". Start aborts
- rename the install path with latin chars
-> OOo starts normally
Comment 1 Mathias_Bauer 2005-11-03 12:52:18 UTC
Obviously the file access of the ResourcManager fails. AFAIK it uses
SvFileStreams for this. PL told me that these streams nowadays also use OSL
(otherwise using them would be a bug IMHO). It seems that osl has problems with
Thai characters in file names.
Comment 2 hennes.rohling 2005-11-10 15:16:53 UTC
Besides that Win XP and espacially NTFS support complete Unicode filesnames 
there is still many code that converts filenames using system codepage. The 
system codepage is always the codepage corresponding with the native language 
of the OS not the selected locale.

Therefore using file names or paths with special characters is only supported if the 
native language of the OS uses a compatible codepage.
Comment 3 hennes.rohling 2006-02-09 09:46:25 UTC