[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 User amy2008 changed the following: What|Old value |New value Status|VERIFIED |CLOSED --- Additional comments from amy2...@openoffice.org Tue Mar 31 03:06:45 + 2009 --- Verified in OOo310m7 on WinXP and Fedora9. Closing Li Meiying - 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...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 --- Additional comments from vladimir_hiteksch...@openoffice.org Mon Mar 30 05:43:47 + 2009 --- Issue 95865 has been fixed in master version OOo-dev 3.1 .0 (OOO310m7 Build:9393)for Windows XP and can be closed. - 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...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 User msc changed the following: What|Old value |New value Status|RESOLVED |VERIFIED --- Additional comments from [EMAIL PROTECTED] Fri Dec 5 12:41:38 + 2008 --- verified in CWS dba31f find more information about this CWS, like when it is available in the master builds, in EIS, the Environment Information System: http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31f - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 User fs changed the following: What|Old value |New value Assigned to|fs|msc --- Additional comments from [EMAIL PROTECTED] Sat Nov 22 19:33:05 + 2008 --- fs->msc: please verify in CWS dba31d - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 --- Additional comments from [EMAIL PROTECTED] Thu Nov 20 10:18:55 + 2008 --- damn, committed the fix to a wrong CWS (dba32a instead of dba31d). Need to copy the fix. - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 User fs changed the following: What|Old value |New value Status|STARTED |RESOLVED Resolution| |FIXED Status whiteboard| |dba31d --- Additional comments from [EMAIL PROTECTED] Thu Nov 6 09:39:30 + 2008 --- I implemented a workaround in CWS dba31d. For this purpose, I duplicated mst's change to move the IsValidZipEntryFileName function to comphelper, and now this function is used to check the to-be library names. Invalid characters are now replaced by _. To prevent the new names consisting of underscores only (e.g. in laguages where usually the complete form name consists of invalid characters), I applied a heuristics which will use a unique number instead of the form name, to construct the library name. - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 --- Additional comments from [EMAIL PROTECTED] Wed Nov 5 12:06:34 + 2008 --- Hm, I still can not find the old issue I have mentioned, may be that was only a wish to open one. - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 --- Additional comments from [EMAIL PROTECTED] Wed Nov 5 11:23:06 + 2008 --- mav->fs: Unfortunately I can not guaranty it, but I will do my best to get it. Actually I have a similar issue I have opened for myself about five years ago, and as always, without a scenario that needs it, the priority was not high enough to let it be fixed. Now we have a number of scenarios. :) - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 --- Additional comments from [EMAIL PROTECTED] Wed Nov 5 11:13:50 + 2008 --- for the record: Talked with AB, and at least he cannot imagine a particular place where non-ASCII library names would actually cause problems (though he also admits this doesn't mean there *is* no such place). As a consequence, if issue 95409 were fixed in a timely manner, then this issue here boils down to check how the Basic runtime copes with non-ASCII library names. - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 --- Additional comments from [EMAIL PROTECTED] Wed Nov 5 11:12:11 + 2008 --- fs->mav: great to hear. I see they're targeted to OOo 3.1 - does this still hold? Do you have an estimation when you will address the issues (in particular 95409)? - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 --- Additional comments from [EMAIL PROTECTED] Wed Nov 5 10:59:42 + 2008 --- There is already two issues related to the problem. The first one ( issue 95408 ) requires that the package does the check for invalid names. The second one ( issue 95409 ) requires possibility to use the unicode stream names. - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 User fs changed the following: What|Old value |New value CC|'mav' |'ab,mav' --- Additional comments from [EMAIL PROTECTED] Wed Nov 5 10:32:55 + 2008 --- In any case, we should fix our API implementation for Basic libraries and storages/packages: Currently, *none* of the involved components rejects invalid names, they're silently accepted, destroying data this way. (There are assertions in non-product versions, but they're of no real-life help in this situation, they should instead be exceptions.) - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 User fs changed the following: What|Old value |New value CC|''|'mav' --- Additional comments from [EMAIL PROTECTED] Wed Nov 5 10:24:52 + 2008 --- fs->mav: It seems that the ZIP package implementation is not capable of dealing with non-ASCII characters. Is this true? Am I correct in assuming that this is a limitation of our implementation only (Given that the command-line ZIP is well able to add a file named "Ä" to an .odb file.)? Is it possible, with reasonable effort, to fix the package implementation? - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 User fs changed the following: What|Old value |New value Status|NEW |STARTED Target milestone|--- |OOo 3.1 --- Additional comments from [EMAIL PROTECTED] Wed Nov 5 10:00:50 + 2008 --- Should surely be fixed before release of the 3.1. - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 --- Additional comments from [EMAIL PROTECTED] Wed Nov 5 09:59:47 + 2008 --- Created an attachment (id=57710) document to reproduce the bug case - 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]
[dba-issues] [Issue 95865] migrating macros in a form with non-ASCII name loses al macros
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95865 Issue #|95865 Summary|migrating macros in a form with non-ASCII name loses a |l macros Component|Database access Version|DEV300m35 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P2 Subcomponent|none Assigned to|fs Reported by|fs --- Additional comments from [EMAIL PROTECTED] Wed Nov 5 09:59:09 + 2008 --- - open the attached database document => a message pops up saying that the document contains macros inside forms, and that you should migrate those to the database document - Tools / Migrate Macros ... => the macro migration wizard pops up - go to the wizard, leaving all options at default => the wizard claims success - close the Wizard with OK => the database document is reloaded - double-click the contained form to open it => an error box pops up saying that a macro could not be found The form contained a macro, which was bound to the OnLoad event of the form. After the migration, this macro (the complete macro library, actually) is lost. This seems to be caused by the non-ASCII character in the form's name. If you do all the above in a non-product version, then you're slain by dozens of assertions saying something about character encoding and non-ASCII characters, both during the migration and when loading the database document after the migration. - 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]