search

substance / texture

A visual editor for research.
MIT License
1k stars 84 forks source link

Is time to a custom break? #937

Open ppKrauss opened 6 years ago

ppKrauss commented 6 years ago

Congratulations to the v1.0! A new era is coming for Texture... The production.

CSS3-break is about the production of good PDF and good paged media (HTML5 + CSS3break), including browsers with good support for print and modern EPUB readers. CSS3-break is "CSS Fragmentation Module Level 3", a W3C Candidate Recommendation of February 2017 that is near (!) to be a Recommendation, Chorme passed in 13 of 14 tests, Firefox in 10.

It is a new north to investment in the Editorial Sector, ~5 or 6 years after dead of XSL-FO, the real "paged media" will born in the open-standards ecosystem.

Well, it is really about Texture? Yes: is an issue suggestion, to say "please, break here"... Will be good if Texture offer the inclusion of optional breaks... In some aspect is analog to offer an interface to soft hyphen (­) or nbsp. For example I preffer to use ISO 9000 instead ISO 9000, is my taste, my layout preference but it is not in the CSS, I need to insert nbsp into XML.
The user must to place it where imagine the future layout-need. And XML-parser can't "clean" it.

Example: to insert an any or always break-* instruction before or after some table-wrap or boxed-text. Perhaps there are no JATS direct way to do it (e.g. attributes or something like HTML's <div class="doSomeBreakHere"/>), but user need to preserve it in the workflow before print... And sometimes we need to back in the workflow, so ideal all in the same XML.

PS: a suggestion, to use "1.0.0" instead "1.0", to be a semantic versioning.

obuchtala commented 6 years ago

@ppKrauss

Regarding 'break': we want to investigate the topic print in general, While this might suggest adding means for manual layout, such as a manual page break, we would like to avoid that as Texture is not meant to be used for editing layout. For the same reason as mentioned in the JATS documentation for the line-break element <break>.

Regarding version: We want to use '1.0' scheme for the Application to hide this extra complexity to regular users which typically find the 'x.x.x' scheme unnatural, but internally we use x.x.x in the package.json.