Timeline for Convert RTF to HTML when it's saved to the database or when it's rendered?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 8, 2020 at 19:30 | comment | added | Coupcoup | That's definitely one of the benefits of preserving the original data. Per the other comment I implemented it this morning to store both rendered html and the rtf in the db. If it needs to change to markdown or something now it'd just be a short script to use the rtf field for each post to convert to the new format and update the rendered column | |
| Dec 8, 2020 at 19:15 | comment | added | Alexander | E.g. What if you decide you want to render to Markdown instead of HTML? If you store HTML, now you need to parse it back to some simpler form, and transform it back to markdown. If RTF is the simpler format of the two (IDK if it is), then I would store that. | |
| Dec 8, 2020 at 16:27 | vote | accept | Coupcoup | ||
| Dec 8, 2020 at 15:55 | answer | added | Phill W. | timeline score: 1 | |
| Dec 8, 2020 at 2:41 | history | edited | Coupcoup | CC BY-SA 4.0 | added 5 characters in body |
| Dec 8, 2020 at 2:28 | comment | added | 1201ProgramAlarm | You're missing a third alternative: Keep both the original RTF version and the generated HTML. (This is what Stack Exchange does.) | |
| Dec 8, 2020 at 1:49 | comment | added | Coupcoup | Updated the pros/cons | |
| Dec 8, 2020 at 1:48 | history | edited | Coupcoup | CC BY-SA 4.0 | added 442 characters in body |
| Dec 8, 2020 at 1:24 | comment | added | 1201ProgramAlarm | Could you elaborate the pros and cons of both methods in your question? | |
| Dec 8, 2020 at 0:34 | history | asked | Coupcoup | CC BY-SA 4.0 |