Treat URL! as normal strings with no encoding behavior #655
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
While Rebol2, R3-Alpha, and Red attempted to apply some amount of
decoding (e.g. how %20 is "space" in http:// URL!s), this changes to
leave URLs "as-is".
This serves the goal that a URL may be copied from a web browser bar,
printed/molded out, and pasted back round-trip. It also means that the
URL may be used with custom schemes (odbc://...) that have different
ideas of the meaning of characters like `%`.
The current concept is that URL!s typically represent the *decoded*
forms, and thus express unicode codepoints normally...preserving
either of:
https://duckduckgo.com/?q=hergé+&+tintin
https://duckduckgo.com/?q=hergé+%26+tintin
Then, the encoded forms with UTF-8 bytes expressed in %XX form would be
converted as STRING!, where their datatype suggests the encodedness:
{https://duckduckgo.com/?q=herg%C3%A9+%26+tintin}
(This is similar to how local FILE!s, where e.g. slashes become
backslash on Windows, are expressed as STRING!.)
This was referenced Feb 15, 2020
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.
While Rebol2, R3-Alpha, and Red attempted to apply some amount of
decoding (e.g. how %20 is "space" in http:// URL!s), this changes to
leave URLs "as-is".
This serves the goal that a URL may be copied from a web browser bar,
printed/molded out, and pasted back round-trip. It also means that the
URL may be used with custom schemes (odbc://...) that have different
ideas of the meaning of characters like
%.The current concept is that URL!s typically represent the decoded
forms, and thus express unicode codepoints normally...preserving
either of:
Then, the encoded forms with UTF-8 bytes expressed in %XX form would be
converted as STRING!, where their datatype suggests the encodedness:
(This is similar to how local FILE!s, where e.g. slashes become
backslash on Windows, are expressed as STRING!.)