-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sub/sup regression in 3.7.0 TXT #634
Comments
@cabo@tzi.org commented RFC 8949 says:
which now would changed in a re-rendering. E.g.,
would become
which may or may not mean the same thing to readers. |
@cabo@tzi.org changed component from |
@cabo@tzi.org commented (fixed component not to be vocabulary, which doesn't seem to get worked on) |
@rjsparks@nostrum.com changed status from |
@rjsparks@nostrum.com commented Can you provide a real example where this has been a problem? This is a result of a requested change, driven by Martin and Lars, which was accepted by the CMT to simplify the text rendering. See #590. The reaction to this change has been positive. This may be an edge case that we need to consider creating different behavior (when text immediately follows the sub). |
@cabo@tzi.org commented The problem is that we have a canonical form that makes the structure perfectly clear, and an HTML/PDF rendering that is not much worse. So the TXT form is always going to be an afterthought, and each time you tweak it in one direction, it gets worse for something else. Changing the canonical form/HTML/PDF to fix the TXT is a non-starter. |
@martin.thomson@gmail.com commented That idealogy has not been strictly adhered to. Why bother pretending that it needs to. There are a few other places where XML contains instructions that are only executed for the text rendering. The same can apply here. |
@martin.thomson@gmail.com changed _comment0 which not transferred by tractive |
@cabo@tzi.org commented Nice. Maybe more like |
@martin.thomson@gmail.com commented I would not include the caret in txtl, or move it to a different attribute (with a default value). Otherwise this seems like a good direction to me, though I caution that the defaults are not as simple as that. |
@cabo@tzi.org commented OK, |
@cabo@tzi.org changed _comment0 which not transferred by tractive |
@cabo@tzi.org commented The brokenness of #590 is already being discussed there under "space". |
@rjsparks@nostrum.com commented Per CMT discussion today, we'll pursue the simple paren="true" mod on the existing implementation, but not try to go down the path of finer-grained control. |
@mahoney@nostrum.com commented RFC 9043 (currently in AUTH48) would benefit from this paren="true" enhancement. In RFC 9043, a_b is constructed ab and represents the value of a sequence. slice_x is a variable name. It is unclear in the text file which is a subscript and which is not. (I also mentioned this in ticket #574). https://www.rfc-editor.org/v3test/rfc9043.xml |
@cabo@tzi.org commented Re the CMT result (comment 11):
I cannot agree with the decision not to provide that. |
@cabo@tzi.org commented Re RFC-to-be 9043: |
type_defect
| by cabo@tzi.orgFoobarbaz
renders correctly in HTML
had a recognizable surrogate in TXT in 3.5.0: Foo_(bar)baz
is munched up in TXT in 3.7.0: Foo_barbaz
Issue migrated from trac:634 at 2022-02-08 07:15:03 +0000
The text was updated successfully, but these errors were encountered: