-
Notifications
You must be signed in to change notification settings - Fork 4
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
Definitions' scopes are too broad #25
Comments
Well, that didn't work. We we have no definitions appearing at all. |
Ah, I think the problem is from #26. Perhaps this fix did work. |
This looks a bit better
I mean, other than the obvious case problem ( |
This looks better:
Except that there are still no global definitions. |
Ah-ha—the problem was define('GLOBAL_DEFINITIONS', '1,2.1'); instead of this: define('GLOBAL_DEFINITIONS', '1,2.1,2'); Previously, we used the SGML, which only included titles and chapters. But now the XML includes subtitles, parts, and articles, and definitions are found within Article 2 of Title 1, Chapter 2.1. So the prior scope wasn't working. I updated |
A lot of definitions are scoped globally, despite that there's nothing in the text that should lead to that. My best guess is that this is from
State::extract_definitions
opening with$scope = 'global'
, setting the default scope to global. (It's also possible that we start with this for perfectly good reasons.) Step through the code while scraping definitions to figure out what's up.The text was updated successfully, but these errors were encountered: