Skip to content
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

UTF8 for the win + lot of housekeeping #12

Merged
merged 10 commits into from
Jan 8, 2024
Merged

Conversation

burner
Copy link
Contributor

@burner burner commented Oct 10, 2022

IMO if this is to end up in phobos UTF8 is the way to, this also means no DOMstring.

The rest is mostly boring housekeeping and formatting.

@ZILtoid1991
Copy link
Owner

Phobos is no longer the target, but I might think about it.

@burner
Copy link
Contributor Author

burner commented Oct 11, 2022

Phobos is no longer the target, but I might think about it.

What is the target now?

@ZILtoid1991
Copy link
Owner

What is the target now?

I'm collecting some input on it from others.

@ZILtoid1991
Copy link
Owner

After some thinking, I came to this conclusion:

  • Keep the XMLChar alias as a configurable template.
  • Ditch the DOMString class and turn it into an alias alias DOMString = const(XMLChar)[].

Even if I decide to later put it out as a Phobos candidate, it'll be easy to undo it, currently it might be more beneficial to keep some configurability of the library. Sometimes it's more practical to use UTF16 or something else (certain East Asian texts benefit from that), which is standard for XML DOM.

@ZILtoid1991
Copy link
Owner

Okay, it's time to swallow the poison pill for my projects.

Accepting it, but likely will keep the 0.2.1 version around for a while.

@ZILtoid1991 ZILtoid1991 merged commit 2c17e0e into ZILtoid1991:main Jan 8, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants