From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
luigi scarso <luigi.scarso@gmail.com>
Subject: Re: ConTeXt as a service
Date: Sun, 24 Nov 2019 12:00:36 +0100 [thread overview]
Message-ID: <7b5529de-1aa9-1433-f9c9-1247bbb25b95@xs4all.nl> (raw)
In-Reply-To: <CAG5iGsBt0Z8mDvPystpqFk6fMfaOoK4ovYS=Avi_z1UxW+__uA@mail.gmail.com>
On 11/23/2019 1:18 PM, luigi scarso wrote:
>
>
> On Sat, Nov 23, 2019 at 1:02 PM Henning Hraban Ramm <texml@fiee.net
> <mailto:texml@fiee.net>> wrote:
>
>
> Don’t exaggerate. Or maybe your company didn’t think about which
> tags are really necessary.
> A proper configuration that doesn’t allow nonsense, even if users
> paste text from Word documents, is not such a big effort.
>
> I can’t remember which JS editor I used >10 years ago for the
> editorial system of a city magazine, but I remember I only allowed a
> few tags (authors weren’t allowed to use font and color settings)
> and also run a HTML cleaner before saving. It was an effort until it
> worked, but not that much.
>
>
> another link:
> https://coko.foundation/
> https://coko.foundation/product-suite/
Sounde nice but then tne question is: which of these will stay for a
long term (commitment, open etc). Always a bit of a ganmble.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-11-24 11:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 16:07 Denis Maier
2019-11-20 16:43 ` Hans Hagen
2019-11-20 17:10 ` Henning Hraban Ramm
2019-11-20 18:50 ` Hans Hagen
2019-11-22 7:43 ` Jan U. Hasecke
2019-11-22 8:46 ` Mojca Miklavec
2019-11-22 9:05 ` Henning Hraban Ramm
2019-11-22 15:45 ` Jan U. Hasecke
2019-11-22 23:44 ` denis.maier.lists
2019-11-23 7:12 ` Mojca Miklavec
2019-11-23 12:02 ` Henning Hraban Ramm
2019-11-23 12:18 ` luigi scarso
2019-11-23 13:18 ` Henning Hraban Ramm
2019-11-23 14:03 ` mf
2019-11-24 11:00 ` Hans Hagen [this message]
2019-11-23 14:14 ` Mojca Miklavec
2019-11-23 15:39 ` Henning Hraban Ramm
2019-11-23 15:50 ` Mojca Miklavec
2019-11-23 16:03 ` Henning Hraban Ramm
2019-11-24 10:56 ` Hans Hagen
2019-11-23 14:24 ` mf
2019-11-23 15:39 ` mf
2019-11-24 10:51 ` Hans Hagen
2019-11-21 2:00 Brian Ballsun-Stanton
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=7b5529de-1aa9-1433-f9c9-1247bbb25b95@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=luigi.scarso@gmail.com \
--cc=ntg-context@ntg.nl \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).