htacg / html-tidy.org

Contains the html-tidy.org website

README for HTACG GitHub Pages

This repository consists of the HTML Tidy homepages.

For ease of maintenance by multiple contributors HTACG's GitHub pages take advantage of GitHub’s Jekyll integration. Therefor it is necessary to be slightly familiar with Jekyll and GitHub’s implementation of Jekyll in order to make changes to our sites.

References

Everything you need to know about Jekyll can be found on jekyllrb.com.

About Github and HTACG Pages

The HTACG group main project page is served from files located in https://github.com/htacg/htacg.github.io. It can be reached from http://www.htacg.org or http://htacg.github.io. The latter is the standard means of accessing the project page, however the former works because we've set up a domain name and configured GitHub to use the domain name via the CNAME file in the repository.

HTACG Project pages are available as subdirectories of the HTACG domain, for example:

• http://www.htacg.org/html-tidy
• http://www.htacg.org/binaries
• etc.

In general this is intuitive behaviour of GitHub pages but it can cause some issues with relative paths used for project web pages. For example:

The HTML-Tidy main project page is served from files located in https://github.com/htacg/tidy-html5/tree/gh-pages. It can be reached from http://www.html-tidy.org, or as above, from http://www.htacg.org/html-tidy.

This is where resource paths can be an issue. Thus it's important to follow the advice given on Jekyll's site. This will ensure that resources such as stylesheets and images are served from the appropriate directory.

In summary use the site.baseurl variable as described in the linked document, and when performing local previewing start Jekyll's server with:

jekyll serve --baseurl ''

or

bundle exec jekyll serve --baseurl ''

Specifying the baseurl on the command line will override the base URL set in _config.yml.

About Binaries

Coming Soon.

About API and Quick Reference Documentation

These are all now stored in the tidy-html5-api repository, and links to them should be to http://api.html-tidy.org. Documentation should be placed into the tidy directory, and entries can be added to the appropriate files in index\_posts.

html-tidy.org's Issues

html-tidy site does not work with https

The site:

http://www.html-tidy.org/

does not work when loaded with an HTTPS scheme because it loads it resources explicitly over HTTP, and some browsers do not like switching from secure to insecure connections when loading resources.

The fix is to change all of the explicit "http://" resource-loading URLs to "//" (removing the http: prefix), which will allow it to work with both http and https.

Project logo is lossy/blurry

Doesn't look nice/professional. Probably needs to be redone if a non lossy version doesn't exist

Segfault of example program

Dear all,

I remarked that the program presented within the post 2000-04-01-part_sample_program produces a SEGFAULT signal if it used as if.

noelm@computer:~/workspace/tidy-html5$ gcc -Wall -g -I./include/ -o basic basic.c -L./build/ -ltidy
noelm@computer:~/workspace/tidy-html5$ ./basic 
Tidying:	<title>Foo</title><p>Foo!
A severe error (-1) occurred.
Segmentation fault (core dumped)

with basic.c which contains exactly the example code mentioned before.

By running gdb I observed with a breakpoint at line 40:

(gdb) l 40  
40	  tidyBufFree( &output );
(gdb) b 40
(gdb) r
(gdb) p output
$1 = {allocator = 0x0, bp = 0x0, size = 0, allocated = 0, next = 0}
(gdb) c

then it segfaults.

I'm on my way to find this bug by comparing console/tidy.c:int main() and the example code.

Regards,
Noel.

Gemfile.lock issue

Get this report...

We found potential security vulnerabilities in your dependencies.
Some of the dependencies defined in these manifest files have known security vulnerabilities and should be updated:

Gemfile.lock 4 vulnerabilities found
Only users who have been granted access to vulnerability alerts for this repository can see this message.
Learn more about vulnerability alerts

How to fix? feedback welcomed... thanks...