Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementing textRuns in RTF & ODT Writer #99

Closed
stSaHiB opened this issue Mar 10, 2014 · 3 comments
Closed

Implementing textRuns in RTF & ODT Writer #99

stSaHiB opened this issue Mar 10, 2014 · 3 comments

Comments

@stSaHiB
Copy link

stSaHiB commented Mar 10, 2014

$this->_writeTextRun($objWriter, $element);
is not yet implemented, in both (basic) writers.

Unfortunately the HTML to docx Converter (http:https://htmltodocx.codeplex.com/) makes heavy use of textruns, so if you want to export userinput, made by a WYSIWYG Editor, to .rtf or .odt, there is currently no possibility for that.
So implementing at least this function would make the 2 writers become more usefull...

thx!
sahib

@Progi1984
Copy link
Member

@stSaHiB Hi, I just merged the pull request from @ivanlanin in the develop branch with its support of ODT and RTF. Could you test and give us your feedback ?

@ivanlanin ivanlanin self-assigned this Mar 16, 2014
@stSaHiB
Copy link
Author

stSaHiB commented Mar 22, 2014

wow, that was amazing fast. didnt expect that feature that soon, so i havent checked this issue recently.

Well, I tested it: RTF now works fine with the HTML to docx Converter, while ODT will export the blank Text without any formating like bold, italic, etc

So, it works not perfect but good enough for me! Of course the formatting and the other elements like peagebreaks, still have to be done, but I was just asking for the textRuns and they are working now. Thx!

One last thing: when writing to rtf I have to utf8_decode the html code, before adding it, while exporting it to odt or docx doesnt need that conversion. Thats no problem for me, but it would be nice, if the writer class can handle it by itself...

@ivanlanin
Copy link
Contributor

Hi @stSaHiB. Thanks for testing. Glad it helps (for now). I close this issue and submit a new issue for UTF-8 support here: #158

@Progi1984 Progi1984 added this to the 0.8.0 milestone Mar 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants