Hi Vincent,
Let me just give you some general information that might help (I have
not yet started to work on the border properties part of bug 12591).
When we use copy & paste, we export to RTF (copy) and then reimport
from RTF (paste).
For frames, the RTF importer is defined in
ie_imp_RTFObjectsAndPicts.cpp and we can see which frame parameters
can be imported by looking at the function IE_Imp_RTF::addFrame. By
comparing with the complete list of frame properties (the best place
to get this list is by looking at fl_FrameLayout::_lookupProperties),
we can find out which properties needs to be added to the RTF importer
in order to have a fully working copy/paste command. I haven't looked
too much at the exporter (it is defined in
ie_exp_RTF_listenerWriteDoc.cpp), but we can guess that the properties
that haven't been defined in the import filter haven't been defined in
the export filter either.
Simon
2012/4/18 vincent vincent <vincent.abiword@gmail.com>:
> Hi Simon,
>
> What's about your investigation about this bug?
> http://bugzilla.abisource.com/show_bug.cgi?id=12591
>
> I also focus on this bug last week (it is related with my GSOC
> project: Text box improvements ). In fact, most of the properties are
> missing while copy & paste.
>
>
> I put a long time to track the process of 'Copy & Paste'. At the very
> begin, I was thinking the two reasons which cause this issue:
> 1. the properties missing in Copy process (Missing the property to Clipboard )
> 2. the properties missing in Paste process (Render issue)
>
>
> But I find that the detailed implementation is very complex, so I want
> to hear more about your advices, Correct me if I have sth wrong.
>
>
> thanks,
> Vincent
>
>
> 在 2012年4月16日 下午5:59,Martin Sevior <msevior@gmail.com> 写道:
>>
Received on Mon Apr 23 09:49:51 2012
This archive was generated by hypermail 2.1.8 : Mon Apr 23 2012 - 09:49:52 CEST