-
Notifications
You must be signed in to change notification settings - Fork 88
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
TEI example is old-formatted #2314
Comments
Good grief! This example is FUBAR. Need to dig through old versions of DI to see if a version that is not messed up can be found. Will try to do that early this week. (Thank you, @kzhr !) |
(DI-PrintDictionaries.xml line 3038.) |
It's not an example of TEI encoding, nor is it "FUBAR" ! (not an expression I would have expected from Syd ) It's an example of a non-TEI XML encoding which can't be transferred directly without using entryFree. That's what the surrounding text says anyway. If there;s anything to fix here, it's the formatting. Maybe wrapping this in a CDATA section would be a good idea? |
P.S. And there is a source citation too: but it's been given as a |
Indeed, @lb42, good point. I just read the prose and came back here to say essentially the same thing, and found you beat me to it! I think this example should probably be wrapped in an |
Per my suggestion on the ticket, changed example of non-XML encoding from 'egXML' to 'eg', and moved citation to its source= attr. Note: The little anchor that shows up for the “link-to-me” feature is the wrong character (i.e., is different than the one used for 'egXML's); and the “bibliography” link is not showing up. Both of these are Stylesheets problems, and neither one should prevent us from incorporating this change, IMHO.
A TEI example cited below seems to be old-formatted and poorly displayed. I'm not sure what it should be.
https://tei-c.org/release/doc/tei-p5-doc/en/html/DI.html#index-egXML-d54e79590
A bit confusing is that this example lacks a source citation. If I remember correctly, it should have a source citation in early 2020, but I can't find recent changes around here.
The text was updated successfully, but these errors were encountered: