search

scottkleinman / aeme

AEME Development Repo
1 stars 2 forks source link

Schema does not allow `gap@reason` #84

Closed scottkleinman closed 8 years ago

scottkleinman commented 8 years ago

This may apply to other attributes listed at http://scottkleinman.net/wp-content/uploads/guidelines-4.0/The_text_Section/Unclear_or_Illegible_Characters.

This bug was raised in issue #83.

skgoetz commented 8 years ago

Hi! On it--wait a bit.

skgoetz commented 8 years ago

I would like an example, possibly a screen shot, from @mmwwah or @scottkleinman.

<gap is a core element, and @reason is on it by default. (The delay is so that I could check my possibly faulty memory against P5 core.) I've loaded the 0.3.5 customization file in Roma, and it confirms that gap[@reason] is available. In junius1.xml straight from GitHub, I am able to insert gap in a random p and assign a @reason. Please clarify the bug report.

I've fixed an unrelated oversight in entities.dtd while glancing over junius1.xml.

skgoetz commented 8 years ago

After rereading #83, I suppose I'm asking only @scottkleinman for clarification?

scottkleinman commented 8 years ago

Strange. It works for me now. It must have been a blip or some other nearby error that caused it to fail validation. Thanks for checking, Sharon. I'm glad you found the bug in entities.dtd so it wasn't a complete waste of your time.