From: Jude DaShiell <jdashiel@panix.com>
To: help-gnu-emacs@gnu.org
Subject: re: web design
Date: Mon, 1 Jan 2018 23:46:40 -0500 [thread overview]
Message-ID: <alpine.NEB.2.21.1801012335440.18996@panix1.panix.com> (raw)
html-tidy can certainly check web site grammar and perhaps repair it too.
I write perhaps since I suspect it is entirely possible to write an html
site so badly that not even html-tidy could repair the site.
One possible direction gnu tools might take in the future would be in
terms of scripts first to install when necessary Linux tools and use those
locally then send site files out for further checking and perhaps
processing and collect those the external sites processed for the
developers. Multiple subdirectories with names of internal and external
tools on them could hold the processed content as the content got
processed and returned. It would then be up to the site developers to
review what was returned in each subdirectory to find if any of the
processing tools made unacceptable errors. html-tidy I consider a hybrid
since the tool can check and slso repair web site files as opposed to
w3cvalidator which so far as I know only checks web site files. My nephew
who could use Windows prefers Linux for his web development he does for
other companies so if any of this starts happening I think he'll be very
interested and may even be making some technical contributions sooner or
later.
--
next reply other threads:[~2018-01-02 4:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 4:46 Jude DaShiell [this message]
[not found] <mailman.6776.1515009232.27995.help-gnu-emacs@gnu.org>
2018-01-03 20:39 ` web design Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2018-01-03 19:53 Jude DaShiell
[not found] <mailman.6696.1514868412.27995.help-gnu-emacs@gnu.org>
2018-01-02 5:05 ` Emanuel Berg
2018-01-02 6:33 ` Kendall Shaw
[not found] ` <mailman.6697.1514874827.27995.help-gnu-emacs@gnu.org>
2018-01-02 16:39 ` Emanuel Berg
2018-01-03 14:55 ` Kendall Shaw
[not found] ` <mailman.6767.1514991340.27995.help-gnu-emacs@gnu.org>
2018-01-03 17:59 ` Emanuel Berg
2017-12-30 1:47 Web Design M. R.P.
2017-12-30 3:39 ` Emanuel Berg
2017-12-30 4:24 ` Rusi
2017-12-30 5:17 ` Emanuel Berg
2017-12-30 12:35 ` Rusi
2018-01-01 18:12 ` Kendall Shaw
[not found] ` <mailman.6672.1514830394.27995.help-gnu-emacs@gnu.org>
2018-01-01 21:55 ` Emanuel Berg
2018-01-02 0:01 ` MBR
2018-01-02 0:21 ` Emanuel Berg
2018-01-02 0:45 ` Kendall Shaw
[not found] ` <mailman.6691.1514853943.27995.help-gnu-emacs@gnu.org>
2018-01-02 0:52 ` Emanuel Berg
2018-01-04 5:04 ` Kendall Shaw
[not found] ` <mailman.6800.1515042320.27995.help-gnu-emacs@gnu.org>
2018-01-04 20:43 ` Emanuel Berg
2018-01-04 20:48 ` Emanuel Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.NEB.2.21.1801012335440.18996@panix1.panix.com \
--to=jdashiel@panix.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.