Is there any area where you would be interested to help? I would
suggest contributing to the exporter, as that one is not under heavy
development.
Interested? Yes
Capable? Alas, at the present a very sad no. C looks like hieroglyphs
compared the near-english Pick-Basic Database Language I use: I can read
and recognize some the C words, but the C syntax is confusing.
Would anyone happen to know of a tutorial program on the internet from
which I could learn the necessary C syntax in order to develop the rtf
importer/exporter?
A download link perhaps?
Until now, I have never had a need or reason to learn C.
Still, if you could put a table to the wiki containing those 66 ...
Yes, I will do that if someone would explain to me how to do that.
I have a couple of HTML tutorials circa msOffice97
Thanks, Tracey
Miklos Vajna [via Document Foundation Mail Archive] wrote:
On Mon, Jul 04, 2011 at 12:54:58PM -0700, tracey002 <[hidden email]
</user/SendEmail.jtp?type=node&node=3139135&i=0>> wrote:
Using the downloaded source dated June 19th and 20th of 2011.
Except for the RTFScanner.lex file (dated June 19th, 2011) which had
RTF
Controls listed, I ended up searching for the string "RTF_" and assumed
that the uppercase alpha characters that followed are RTF controls
(that
appeared to be the pattern anyway).
Yep, both the old and the new import filter uses RTF_FOO to parse \foo.
The exporter uses OOO_STRING_SVTOOLS_RTF_FOO.
Of the 1807 RTF Controls found in the March 2008 1.9.1 Specification,
1,333 need to be added to the Import Routine and 1,419 need to be added
to the Export Routine (see attached).
Nah, just adding them is easy - the real trick is to implement them. Is
there any area where you would be interested to help? I would suggest
contributing to the exporter, as that one is not under heavy
development.
66 controls used in the import and/or export routine require definition
because they do not appear in the March 2008 1.9.1 Specification (see
attached).
Attachement stripped - probably you need to get an email client instead
of nabble if you want to send attachements.
Still, if you could put a table to the wiki containing those 66
keywords, then we could start writing oneliner documentations for them -
that would be a great start.
_______________________________________________
LibreOffice mailing list
[hidden email] </user/SendEmail.jtp?type=node&node=3139135&i=1>
http://lists.freedesktop.org/mailman/listinfo/libreoffice
*attachment0* (205 bytes) Download Attachment
</attachment/3139135/0/attachment0>
------------------------------------------------------------------------
If you reply to this email, your message will be added to the
discussion below:
http://nabble.documentfoundation.org/RTF-support-tp3114982p3139135.html
To unsubscribe from RTF support, click here
<http://nabble.documentfoundation.org/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3114982&code=d3BpaXNAZ3RlLm5ldHwzMTE0OTgyfDg1NDMxMTYz>.
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.901 / Virus Database: 271.1.1/3745 - Release Date: 07/05/11 01:35:00
No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 9.0.901 / Virus Database: 271.1.1/3745 - Release Date: 07/05/11 01:35:00
--
View this message in context:
http://nabble.documentfoundation.org/RTF-support-tp3114982p3141100.html
Sent from the Dev mailing list archive at Nabble.com.
Context
- Re: [Libreoffice] RTF support (continued)
Re: [Libreoffice] RTF support · Cedric Bosdonnat
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.