To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=100727
                 Issue #|100727
                 Summary|[sw-html] user-defined document info fields messed up
               Component|Word processor
                 Version|OOo 3.0
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|open-import
             Assigned to|mst
             Reported by|mst





------- Additional comments from [email protected] Tue Mar 31 15:37:27 +0000 
2009 -------
it seems i made a mistake when converting the writer html import filter to
DocumentProperties.
if a HTML file created with writer in OOo 2.x contains user-defined document
info fields, then on import in OOo 3.x those fields may be mapped to the wrong
user-defined document info.

this happens because in the HTML format, there are specific subtypes INFO[1-4]
corresponding to the 4 user-defined properties that are visible in the dialog.
the import filter uses the DocumentInfo service to access the 4 properties, but
the service is instantiated too late: after the properties have already been
sorted alphabetically.
solution is to handle the field import differently: the import filter itself
remembers which are the 4 properties (META-elements) corresponding to the 
fields.

---------------------------------------------------------------------
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]

Reply via email to