XSweet issueshttps://gitlab.coko.foundation/XSweet/XSweet/-/issues2022-05-09T12:02:31Zhttps://gitlab.coko.foundation/XSweet/XSweet/-/issues/169Preserve tab spaces2022-05-09T12:02:31ZBharathydasanPreserve tab spacesThe tab characters are actually converted to `<span class="tab"> <!-- tab --></span>` element in initial conversion, but it is removed in the conversion pipeline, this happens at the `15EDITORIABASIC.xhtml` where the span elements are...The tab characters are actually converted to `<span class="tab"> <!-- tab --></span>` element in initial conversion, but it is removed in the conversion pipeline, this happens at the `15EDITORIABASIC.xhtml` where the span elements are removed. well, the track-changes for tab character are preserved properly with `<ins>` and `<del>` which was added earlier.
Only the elements `<pre>` and `<code>` in HTML can render the tab spaces. Here my question is how these tab spaces are handled in `Editoria` or `Wax`.https://gitlab.coko.foundation/XSweet/XSweet/-/issues/167Support options for different handling of track changes2020-09-20T20:46:25ZAlex ThegSupport options for different handling of track changesNow that the basic functionality to extract character insertion/deletion track changes into HTML is part of the initial extraction sheet, it's easy to comment that bit out if that's not desired.
We should consider how to give options to...Now that the basic functionality to extract character insertion/deletion track changes into HTML is part of the initial extraction sheet, it's easy to comment that bit out if that's not desired.
We should consider how to give options to XSweet users who may want to handle track changes differently: accept or reject them all away, drop them at a later stage, etc.
* This could possibly be managed with runtime flags
* We could also have a standalone sheet in the pipeline that a user could tweak to specify how to handle track changes: accept them all, reject them all, etc. This could work by passing in a runtime option, commenting/uncommenting the desired sections, etc.https://gitlab.coko.foundation/XSweet/XSweet/-/issues/166Track changes for tables?2020-10-29T08:27:20ZAlex ThegTrack changes for tables?Tracking changes to tables came up in this week's discussion with @bharathydasan and @wendell. There may not ultimately be a need for this, but if there is, it can come after the initial TC implementation.
This could also be potentially...Tracking changes to tables came up in this week's discussion with @bharathydasan and @wendell. There may not ultimately be a need for this, but if there is, it can come after the initial TC implementation.
This could also be potentially very complex. @wendell suggested that as a way to limit the scope/complexity of a solution, a simple whole-table before/after comparison could be surfaced, rather than a granular representation of the specific changes.https://gitlab.coko.foundation/XSweet/XSweet/-/issues/165Paragraph-level formatting track changes2020-06-17T02:26:16ZAlex ThegParagraph-level formatting track changesThis is a placeholder ticket for handling paragraph-level track changes. See also #162 and #164 for additional context.
Paragraph-level formatting changes will be ignored for a first implementation of track changes. However, they may me...This is a placeholder ticket for handling paragraph-level track changes. See also #162 and #164 for additional context.
Paragraph-level formatting changes will be ignored for a first implementation of track changes. However, they may merit revisiting at some point. From @bharathydasan:
> there are few things stored in paragraph properties such as center, left, and right alignments that need attention