Databases
StackOverflow2013
Postsdbo
POJSFL: convert text from a textfield to a HTML-format string
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJSFL: convert text from a textfield to a HTML-format string
    text
    copied!<p>I've got a deceptively simple question: how can I get the text from a text field AND include the formatting? Going through the usual docs I found out it is possible to get the text only. It is also possible to get the text formatting, but this only works if the entire text field uses only one kind of formatting. I need the precise formatting so that I convert it to a string with html-tags. </p> <p>Personally I need this so I can pass it to a custom-made text field component that uses HTML for formatting. But it could also be used to simply export the contents of any text field to any other format. This could be of interest to others out there, too. Looking for a solution elsewhere I found this: </p> <p><a href="http://labs.thesedays.com/blog/2010/03/18/jsfl-rich-text/" rel="nofollow">http://labs.thesedays.com/blog/2010/03/18/jsfl-rich-text/</a></p> <p>Which seems to do the reverse of what I need, convert HTML to Flash Text. My own attempts to reverse this have not been successful thus far. Maybe someone else sees an easy way to reverse this that I’m missing? There might also be other solutions. One might be to get the EXACT data of the text field, which should include formatting tags of some kind(XML, when looking into the contents of the stored FLA file). Then remove/convert those tags. But I have no idea how to do this, if at all possible. Another option is to cycle through every character using start- and endIndex, and storing each formatting kind in an array. Then I could apply the formatting to each character. But this will result in excess tags. Especially for hyperlinks! So can anybody help me with this?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload