-
Notifications
You must be signed in to change notification settings - Fork 3
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
Display of <expan>
#260
Comments
I never use expansions so I am not directly concerned... I approve of what you propose for Physical and Logical, but I don't see why display should be so undiplomatic in Full. I'd rather the abbreviation be displayed as such with some bracket or symbol marking that it is an abbreviation. The tooltip is not necessary in this display which is intended mainly for copy/pasting to print context. |
I have never used expansions either, and especially the form with an "abbreviation marker" that is not part of the expanded abbreviation is expected to be very rare to nonexistent. It was included in the EGD just in case it occurs one day, because the provision exists in EpiDoc.
Now some general thoughts. I think it is very important that expansions, if they are displayed at all, should be clearly indicated as non-original, preferably with hard markup (brackets of some sort), and not just colour. This applies to logical display as well as to the full one. Given the above, I propose the following, in all display modes:
Beyond this, I'm not sure how far we should go. In my opinion, nothing beyond the above should be done in diplomatic view. I could imagine showing a dagger, as I suggest above, next to the abbreviation in logical and mixed mode, |
I am not sure how I should display abbreviations, depending on the display mode. For:
... I propose:
Is this ok?
We decided to use a background color for
<abbr>
. Should<am>
have a peculiar format, too?So far,
<am>
is not used, and we only find the pattern<expan><abbr>...</abbr><ex>...</ex></expan>
, with a single occurrence of<abbr>
+<ex>
.The text was updated successfully, but these errors were encountered: