-
Notifications
You must be signed in to change notification settings - Fork 13
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
Factor out the DRef library #29
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since we are evaluating arbitrary code anyway.
melisgl
force-pushed
the
dref
branch
4 times, most recently
from
July 6, 2023 21:18
aa801a5
to
21a0b5d
Compare
melisgl
force-pushed
the
dref
branch
11 times, most recently
from
July 13, 2023 13:19
29c806f
to
b13462a
Compare
melisgl
force-pushed
the
dref
branch
11 times, most recently
from
July 16, 2023 18:41
6832d19
to
6abc515
Compare
... which may not be an HTML paragraph (i.e. not in <p>).
For example, when a SECTION was subclassed as CATEGORY, one had to defin a CATEGORY locative, a CATEGORY-DREF, and all the LOCATE/RESOLVE machinery to be able to specialize DOCUMENT-DREF or other generic functions used to extend some operation. With this change, this is no longer necessary because these generic functions are now tried on the RESOLVEd definition (if possible), then on the LOCATEd definition. The net effect is that when there is a perfectly good first-class object for a definition, operations can be extended by specializing on their type without needing to jump through the locative/dref hoop.
... for security reasons.
Characters such as # were not escaped.
The DREF function does what the three argument LOCATE used to.
... so that we know which DREF subclass corresponds to which locative type. This will be needed, for example, for DREF-APROPOS to support matching on subtypes.
melisgl
force-pushed
the
dref
branch
4 times, most recently
from
July 20, 2023 15:23
45869f4
to
bc7690a
Compare
This is finished, I think. I'll probably wait for 3b/3bmd#60 to land because it's a soft dependency then merge this. |
- There are now two HTML styles: :DEFAULT and :CHARTER. PAX:UPDATE-ASDF-SYSTEM-HTML-DOCS defaults to :DEFAULT by default, while the live browser defaults to :CHARTER. - More mobile friendly: remove the table of contents sidebar if the page is too narrow. - Fall back on Georgia for the main fontn if XCharter and Charter are not present. - Fall back on Times New Roman for H1 headings if XEB Garamond is not present. - Make it easier to use a sans-serif font (by editing :root in the CSS). - Remove unused font files.
melisgl
force-pushed
the
dref
branch
2 times, most recently
from
July 21, 2023 16:27
2a183ba
to
f7da049
Compare
This is a hopefully temporary workaround for the Github issue https://support.github.com/ticket/personal/0/2259703. Only affects version 1 URLs (see PAX:*DOCUMENT-URL-VERSIONS*).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.