I agree with BrklynBridge (20 Nov 2011): there are formatting problems WHEREVER users (paying customers) enter text on their trees.
My particular gripe is with STORIES. It should be possible to post stories as text with basic formatting, so that other users can browse a story quickly, without downloading a PDF. Basic formatting (including bullet points and indented paragraphs) can make a story more readable.
ACOM does provide a text editor with text formatting options for stories. But the formatting you see when editing a story bears no relationship to what you get when the story is saved and viewed. Spacing between paragraphs goes awry (space sometimes opens up, sometimes disappears); horizontal spacing (spaces or tab chars) is stripped; bullet points and indents become left-aligned plain text, and so on. Even spaces between words can disappear when a file is saved.
The results are not consistent: various formatting elements are sometimes preserved, sometimes stripped, sometimes distorted. But the result is almost always a mess.
Subscribers who publish trees with rich content add value to the product that ACOM is selling. So come on guys: it’s time to upgrade your online text editor to 1980s standards.
I support the petition