To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=114525


User pl changed the following:

                What    |Old value                 |New value
================================================================================
             Assigned to|pl                        |of
--------------------------------------------------------------------------------
                Priority|P1                        |P3
--------------------------------------------------------------------------------




------- Additional comments from p...@openoffice.org Tue Sep 21 14:57:26 +0000 
2010 -------
P1 is basically reserved "the build is broken" or "the whole OOo does not even
start". A bug like this that you yourself describe as occuring since 3.0 but no
one ever bothered to report does not seem to be in that kind of category.

Moreover I don't have any problems creating/reading files like "fnärp.odt",
"testç.odt" or "testę.odt" using OOo 3.2.1. Also I renamed a file to "zażółć
gęślą jaźń.odt" in Finder and could open it without problems. I could also 
save
a new file in 3.2.1 to that name without problem and it should just like that in
Finder. The same works just fine in OOO330m8, so all I can say is that I cannot
reproduce the issue.

@of: perhaps you can reproduce this problem ?

---------------------------------------------------------------------
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: issues-unsubscr...@framework.openoffice.org
For additional commands, e-mail: issues-h...@framework.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to