Issue 69836 - CurDir() function is not Unicode-compliant
Summary: CurDir() function is not Unicode-compliant
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: ab
QA Contact: issues@api
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-25 13:37 UTC by rail_ooo
Modified: 2013-02-24 21:07 UTC (History)
2 users (show)

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

Attachments
curdir diff (1020 bytes, patch)
2006-09-25 13:37 UTC, rail_ooo 		no flags Details | Diff
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 rail_ooo 2006-09-25 13:37:30 UTC 
Curdir returns garbage if current directory path contains non-ascii characters.
Attached is a patch which converts result according current
gsl_getSystemTextEncoding.
Can you investigate this patch and apply if it is OK?
Comment 1 rail_ooo 2006-09-25 13:37:56 UTC 
Created attachment 39356 [details]
curdir diff
Comment 2 ab 2006-09-27 15:29:06 UTC 
2.1 STARTED
Comment 3 ab 2006-09-28 15:33:22 UTC 
FIXED
Comment 4 ab 2006-10-19 09:55:48 UTC 
Reopen
Comment 5 ab 2006-10-19 09:56:10 UTC 
ab->rail: I realised too late that your code does not work at least for Windows,
as the _getdcwd system call is used that does not support Unicode. Anyway
this is old system dependend code and should be replaced by system inde-
pendend vos API calls. Maybe you want to provide a patch for this?

-> INVALID
Comment 6 rail_ooo 2006-10-19 14:51:31 UTC 
rail->ab: can you provide your test case which not pass?

I use very simple one and it works for me.

1. Run "cmd"
2. mkdir c:\теÑÑ‚
3. cd  c:\теÑÑ‚
4. run OOo via cmd (c:\Program Files\...)
5. Add new module/macro:

Sub Test
  MsgBox CurDir()
End Sub

Box shows proper value.
Comment 7 ab 2006-11-28 07:24:01 UTC 
ab->rail: I can't find my test case any more. But even without it there
is the problem that documentation for _getdcwd says that this is not
the right command for Unicode. Anyway I reopen the tast and will
have another look. This could take some time as currently I'm very
busy,

Reopen
Comment 8 ab 2006-11-28 07:27:36 UTC 
OOo 2.x, STARTED
Comment 9 kai.sommerfeld 2007-02-07 10:30:47 UTC 
Target => 2.3
Comment 10 ab 2007-05-14 11:51:42 UTC 
Still planned for OOo 2.3, but currently no time available for checking again
Comment 11 ab 2007-06-21 15:07:19 UTC 
ab->rail: I had another look now, but still can't verify the patch.
I don't understand how I can start OOo in a way that makes
c:\теÑÑ‚ the current directory. As already stated in i69835 I cannot
access directory containing unicode characters from command
prompt as there only ???? is displayed. cd c:\теÑÑ‚ simply is not
possible on my system (Windows Server 2003 SP1). Any idea?
Comment 12 ab 2007-07-16 10:15:36 UTC 
I have found no way to test the patch and set it back to 
INVALID. If a test case will become available later, the
task can be reopened.
Comment 13 ab 2007-07-24 10:38:36 UTC 
CLOSED