To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=95628
                 Issue #|95628
                 Summary|UserLayer location defaults to boot drive if username 
                        |contains non ansi characters
               Component|framework
                 Version|DEV300m34
                Platform|All
                     URL|
              OS/Version|Windows, all
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|hro
             Reported by|jsk





------- Additional comments from [EMAIL PROTECTED] Thu Oct 30 08:51:16 +0000 
2008 -------
Full, lengthy Reproduction
- Use Windows XP
- Localize it to some western locale (German, en_US, whatever)
- Create a user with a name that contains Asian or Cyrillic characters
- Install the office as administrator (western locale)
- Switch to the Asian/Cyrillic user
- Start the office
-> The user layer will be created in the root of the Windows boot drive
-> All users with strange names share the user layer (locking applies)
-> No installation of extensions is possible (Exception: Operating on read-only
context)

As discussed with HRO this scenario is a rare one. Actually it might only apply
to e.g. foreign workers who insist on having their "un-ascii-fied" name as login
name.

The workaround is to install the language pack for the foreign user.

The root cause for the issue is that some parts of the office code still uses
ANSI strings (hope i got that right) where as most of the office core already is
unicode only. So if a character outside the ANSI table is used we end up not
being able to correctly handle the %USERCONFIG% from the windows registry.

A short term solution would be to warn and abort if the user directory could not
be determined so that we do not write to the boot drive. The long term solution
would be to make the entire office unicode safe which is definitely out of scope
for 3.1.

HRO: Please evaluate the effort and re-target the issue to whatever you find
appropriate

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to