|
@dickloraine: Yes, predefined styles as default and example, while front end styles could be matched to styles the back end would recognizes, too. So one could have predefined or custom styles at the front end or the back end or both, and if needed, a matching would be configured. Ideally, word processors would provide an import and export for style definitions, but even without a template file could be provided for people to write in, and its processibility by the corresponding processing workflow could be guaranteed. The main use case is based on the observation that the ordinary author and even some professionals tend to apply direct formatting for typesetting and e-book generation (since both are incompatible and therefore require duplicate manual work), so it costs either time or money (spent for somebody elses time) or quality. Since some tools which are used for writing don't encourage semantic markup and automated processing workflows aren't accessible enough yet, solving both issues could at least for some provide a better alternative with every new book project. Also, processing texts in bulk and specialized workflows to produce custom output seems to be very attractive for more advanced users, who in most cases need automation in one way or another anyway.
|