Hi all,
there are different approaches to solving this scenario. Three that come instantly to my mind:
- The existence of an ODF application where customers could select the allowed set of ODF features (e.g. disable all automatic styles for some scenarios - like translators) or allow only certain subsets of functionality (a certain type of tables and images must have a caption, etc.), has been a customer wish since my early times at StarOffice 1999. My bet would be that adding this ability to LibreOffice might be the most costly solution.
- The discipline of the editors and the alignment of requirements with predefined styles seem one of the easiest and cheapest solutions. But there would be no validation.
- Nevertheless, as Thorsten mentioned, TDF has well the ODF Toolkit in its portfolio, which contains for instance the ODF Validator and the ODFDOM library for creating, manipulating and reading ODF documents on the server-side using Java. Scenarios like, the listing and later elimination of automatic styles by exchanging them for adequate template styles might be handled by this library for the ODF specification. Also, as you required, some user-specific validation or constraint functions like the check that only one style is applied to a paragraph and one enrichment applied to a word could be added on top of ODFDOM. At least this would be likely my approach to solving the problem.
Have a nice weekend,
Svante
Am Sa., 9. Apr. 2022 um 18:30 Uhr schrieb Andreas Kage <andreaskage@xxxxxx>:
From the view of a publishing scientist and lecturer LO is quite perfect to generate a variety of formats (PDF, ePub etc ) out of the odt file. The odt XML style can excellently handle the different Paragraph Styles (regular, list, legends and such) but also the implementation of different languages (greek, Special European Unicode) as well as other objects such as formulas and more.
What is still missing and might be able to realize with your available budget to s certain extent is a systematic format set of Styles for the different scientific journals and University styles.
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 07.04.22, 19:13 schrieb Yves Picard <yves.picard@xxxxxxxxxxxxxxx>:Hello,
On the advice of Sophie Gautier, I would like to tell you about one of our "research and development" projects, for which I have a budget of about two thousand euros. As a university publisher, we maintain electronic publishing channels from word processing to several publishing formats (html, epub, InDesign, PDF), passing through a pivot format in XML TEI. This pivot format is itself derived from an XML export from Libre Office.
A significant part of our work consists of tracking down and containing artefacts from the word processor (Word or Libre Office), in particular style nesting, automatic styles or language attributes, etc.
I'm looking to test the idea of a "strict" version of LO that would ensure that one style and one style only is applied to a paragraph, that one enrichment and one enrichment only is applied to a word (no use of styles like "accentuation" for example) or that a web link is always findable despite the style applied. This would probably be an "amnesiac" version of LO (without memory of the various manipulations) which would either be used by authors (difficult to set up) or would be used by the editor by loading an author file in this strict version.
An alternative (and probably better) idea would be a "big cleaner" tool that would flatten all style or attribute nesting to the author's work.
I'm looking for an opinion from the Libre Office community on the feasibility of such a development, while being well aware that it goes against the logic of the word processor in some way. But such a version, I believe, would meet the expectations of the publishing world.
Thank you for your attention,
Regards,
Yves Picard,Presses universitaires de Rennes,
France.
