2de72e5070
Partly revert recent changes removing #imports and #includes, under OpenChange, as they cause more problems than they solve.
2016-02-17 10:09:18 -05:00
bd56f4cf9f
Remove pointless #include from .m and .h files
...
This was done with a brute-force approach, ensuring no additional
warnings from GCC 4.9 under x86_64.
2016-02-13 17:41:54 -05:00
b3bc6bb7dc
Applied changes coming from v2/PR#184 .
2016-01-18 09:26:07 -05:00
ae6ed0c055
(feat) applied all changes as a patch coming from PR #180
2015-12-30 09:22:08 -05:00
f2b5f5917b
Fixed dot notation
2015-04-27 15:02:00 -04:00
637ac1e98a
oc-rtf: no color table definition
...
Be able to parse rtf files without color table defined
\colortbl
2015-03-18 18:06:49 +01:00
6e00274988
oc-rtf: safe parse ignoring content
...
Be able to parse safely \*\xxxxx control words with \binXXXX
elements inside it (before final })
2015-03-12 17:13:17 +01:00
f9550b9181
oc: several uninitialized variables
2015-01-19 15:35:44 +01:00
501ee79766
oc-rtf: fix parse \pict tag with \bin data
2014-12-23 11:14:54 +01:00
258444bb93
oc-rtf: Be more resilient to spaces while parsing font tables
...
This avoids to crash on this example:
\f0\fibi \fcharset0
-------^
Or:
\f0 \fibi\fcharset0
--^
Take into account that I found lots of RTF documents with this format:
\f0\fbidi \froman\fcharset0
\f0\froman\fprq2 \fcharset0
Which are not unsupported by this handler.
2014-11-19 17:12:30 +01:00
75ce59d010
oc-rtf: Fix current position to match where _bytes pointer is
...
This avoids to have extra unknown bytes at the end of the RTF document
as _len would have been reached but _current_pos had incorrect less value.
2014-11-19 17:12:29 +01:00
cbfcd54858
oc-rtf: Use what RTF Spec 1.9.1 for control words
...
This reverts 7581c0a.
2014-11-19 17:12:29 +01:00
05578bfcb6
oc-rtf: control words can also have a space before next tag
...
This was causing to parse a single space as an empty control
word with length 0, which was the source of several crashes.
Example:
\f0\fbidi \fcharset0
--------^
font index is 0, font family is bidi but when parsing charset we were
assuming control word was '' instead of 'charset0'.
This only fixes the crashes, the parseFontTable function works quite
awful right now.
2014-11-19 17:12:28 +01:00
5ee8cb3a3f
oc-rtf: check valid font name when generating <font> tag
2014-11-19 17:12:27 +01:00
4e3a242f2f
oc-rtf: Don't crash when we don't know the specified font
2014-11-19 17:12:27 +01:00
99d38417cc
Fix for bug #2354
2013-09-25 13:51:42 -04:00
cd4abe4b5b
Fix for bug 2398
2013-09-06 13:48:44 -04:00
9d9a434fdc
Avoid crashing when reading fcs crap.
2013-06-20 15:44:35 -04:00
6a8e6cd762
Fixed the GNUmakfile and const's for charset tables.
2013-03-28 08:32:00 -04:00
663351029a
Replaced unrtf by our own RTF to HTML converter.
...
Faster, thread safe, a hell lot cleaner.
2013-03-26 19:32:08 -04:00
Patrice Levesque
Ludovic Marcotte
Jesús García Sáez
Enrique J. Hernández Blasco