To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=51121
User obr changed the following:
What |Old value |New value
================================================================================
Status|NEW |STARTED
--------------------------------------------------------------------------------
Summary|desktop/share: creatoin of|desktop/share: creation of
|shared-mime package |shared-mime package
|duplication of effort, bad|duplication of effort, bad
|approach |approach
--------------------------------------------------------------------------------
Target milestone|--- |OOo 2.0
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Wed Jun 29 22:42:14 -0700
2005 -------
> I don't understand that one. I read the components from documents ulf and read
> the mime-type from the $component.desktop files.
Right. I am just saying that this has nothing to do with parsing localize.sdf
vs. merged documents.ulf, which I thought you claimed earlier.
> It is very unlikely that this will change without notice. If it does, the
> various lanugage-communities will rise (since they rely on the fileformat for
> po-file creation), the way the help-index trees are created rely on the format
> as well...
Interesting, didn't know that. Actually I thought of writing the
shared-mime-info import/export in perl myself - I simply don´t understand why
Ivo is coding this in C/C++.
> Why would this involve icon-renaming?
We would have to extend the shared-mime-data format otherwise if we want to
generate *.keys and *.desktop files form it. Renaming text.png to
vnd.sun.xml.writer.png easily solves this problem and is also more compliant to
what is discussed on freedesktop.org as a potential "mime type icon naming"
spec.
? Don't understand that either. Why would you copy translations
Since the file name is used as a key in localize.sdf and because we can not
change localize.sdf directly - it is the export of a database. So when making
the move from documents.ulf to a translated shared-mime-info, we would lose all
translations for a couple of months, which can be avoided by tweaking the
database accordingly.
I'll try to come up with a proposal which incoperates the best of our two
approaches.
---------------------------------------------------------------------
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]
