Apache OpenOffice (AOO) Bugzilla – Issue 50503
"file does not exist" when trying to open filename with non-ASCII chars
Last modified: 2008-05-17 23:25:54 UTC
In m107 from ftp.linux.cz, attempting to open a file whose name contains non-ASCII characters produces an error, claiming that the file does not exist. m102 from the same source opens the file without issue (though it does actually display the non-ASCII characters in the titlebar or in the open/save dialogues like NeoOffice/J). Mac OS X 10.3.9, either StartOOo or Start_OOo2.0.app used as launchers.
looks like the result of some macosx% cws. Can you please test also with ericb's build?
pjanik: unfortunately, I can't test ericb's recent builds (> m93) because they are 10.4.x-only and I am only on 10.3.9. Also, the files do not even show up in the open/save dialogues under your m107, so there is no possibility of opening them without renaming to remove all non-ASCII characters. (Under your m102 "western" characters like é show up in the open/save dialogues but Arabic letters do not display properly; nevertheless, m102 can open docs with either or both types of non-ASCII characters in filenames, both from open/save or the launcher apps.)
This is due to integration of macosx07/#i44530# in m107. fipa: please confirm this issue.
I perfectly know this problem. the solution is in sal/systools/macxp_extras/x11osx/osclocale.c So what happens ? Not like other builders, I always integrate the changes in my own *non official* builds, for tests because I have a lot of french testers. I have proposed the changes in #i44528#, and they were refused because not enough "generic". Since, I'm working on the integration of another solution, from P. Luby, using Carbon framework. Not sure at all that use this framework is very clean on Tiger Note for Pavel : what works in m93 is exactly what I proposed in #i44528# but Maho changes this for an issue with new changes and undefined status now... ( #i46963# ). Two codes were proposed by Etsushi Kato. What works sure for de and fr is the first I use in #i44528#. Maho just tested ja locale, and changed the issue priority because ja locale seems to have problem. The probelm I have not the possibility to fix japanese locale... A third and better possibility consists simply in the use of Cocoa framework, and I'm working on this actually. This last way is IMHO the best, because of the changes since Tiger is out. Hope to be clear... I think this issue is a duplicate of #i44528#, IMHO.
Unconfirmed -> no target yet.
Issue duplicate of #i44528#, and IMHO fixed in #i25416#
ericb: Yes, I agree, this is the old locale/UTF-8 bug, and I wouldn't have filed this issue if things had not gotten worse (completely broken) between the two builds. I'm puzzled that the fix (issue 44530) made things worse instead of better, mais c'est la vie. :-) Please dupe as appropriate, and, as always, I'll be happy to test a build that runs on 10.3.9 that includes the eventual fix :-)
issue fixed in macosx10 + duplicate of 25416 *** This issue has been marked as a duplicate of 25416 ***
The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew