On Tue, Feb 1, 2011 at 3:09 AM, Martin Srebotnjak <[email protected]> wrote:
> 2011/2/1 Stephan Bergmann <[email protected]> > > > See the dev@ooo branch of this mail thread for an analysis of the > problem. > > > > > What? Where is that mailing list? Can't you post just a summary of the > resolution of this bug here? Or do we have to subscribe to 7 mailing lists > to read about a single issue and understand what is going on? Can you make > it more user-unfriendly? > > Lp, m. > I guess it can be posted on the issuetracker. But it might be a malformed XML from the look of it. However I am still not sure what the %origin% environmental variable really points to since the absolute path generates some weird directories example, user instalation creates the following path: /home/<usuario>/.openoffice.org/3/user/extensions/tmp/extensions/ _sdfERl/es_MX/es_MX.aff this random name of a folder makes me wonder if extensions now are more tightly controlled since they need to be registered. This would be a problem for python extensions for example where you need to manually create the files in the Scripts folder. (in case of a registered macros). So before I can just add macros by simply inserting the py file on the Script/python/ folder, but if we have a registry module, now this would be impossible. But I guess that is a different issue all together. Can I ask what is the reasoning for registering extensions and create random paths? -- *Alexandro Colorado* *OpenOffice.org* Español http://es.openoffice.org
