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

Manual MarkDown backup of the original HTML 4.01 documentation #1

Merged
merged 3 commits into from
Jan 27, 2019

Conversation

LorenzoAncora
Copy link

Fix issue clone#1 by creating the missing documentation, because the Wayback Machine is not an ideal source of documentation...
This should be enough to keep these utilities alive for a long time.

The original documentation is disappearing from Internet, along with the author's website.
This is the manual conversion of the original documentation from HTML to MarkDown, so it will be available in the future along with the utilities. The text has been manipulated so as to eliminate unnecessary external references and appear correctly on GitHub and similar.
The original documentation is disappearing from Internet, along with the author's website.
This is the manual conversion of the original documentation from HTML to MarkDown, so it will be available in the future along with the utilities. The text has been manipulated so as to eliminate unnecessary external references and appear correctly on GitHub and similar. The sarcasm of the author has been preserved, as it should be. :-)
The original documentation is disappearing from Internet, along with the author's website.
This is the manual conversion of the original documentation from HTML to MarkDown, so it will be available in the future along with the utilities. The text has been manipulated so as to eliminate unnecessary external references and appear correctly on GitHub and similar.
@LorenzoAncora
Copy link
Author

@cryptorick then? Please, it's been a long time, can you merge the push request?

@LorenzoAncora
Copy link
Author

@cryptorick are you alive? :'-)

@cryptorick
Copy link
Owner

@LorenzoAncora lol yes! :) But I am confused. I only have a fork of a clone here (and I only made it to possibly make a PR to clone/xml2). I am not the author of xml2 nor have any other affiliation with it. I am like you, just someone on the internet who is trying to help. It's sad that Dan (the author) has seemed to drop off and removed the xml2 pages from his websites. I don't know what to do now. I could take your patches, but that would have the same effect as you just holding on to your patches yourself. Hmmm.... The only reason, it seems, to merge your patches here would be a little redundancy (in case one of us disappears or deletes our xml2 fork). Please let me know what you think. Thanks! (And sorry for the delay getting back to you.)

@cryptorick cryptorick merged commit f2d6ba1 into cryptorick:master Jan 27, 2019
@cryptorick
Copy link
Owner

With my disclaimer above, I merged your commits. Now we have two copies on github / the "intertubes." :) Still would like to know your thoughts, @LorenzoAncora, when you get a chance. Cheers! --Rick

@LorenzoAncora
Copy link
Author

LorenzoAncora commented Jan 28, 2019 via email

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