From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt as a service
Date: Sat, 23 Nov 2019 13:02:29 +0100 [thread overview]
Message-ID: <C5DF8B60-BCB3-4E5F-A22A-0FA3B4124C46@fiee.net> (raw)
In-Reply-To: <CALBOmsY0=8bAgZ_6ibxhOL=u+TObuFM6j+sFAYWAD2tPM2hWfg@mail.gmail.com>
> Am 2019-11-23 um 08:12 schrieb Mojca Miklavec <mojca.miklavec.lists@gmail.com>:
>>
>> Then you can use one of the online JS editors like CKeditor.\
>
> Only if you spend an enormous amount of effort making sure that the
> code is properly cleaned up rather than containing a gazillion random
> html style tags which you can never reconstruct back into some
> structured form.
>
> (And yes, my impression is that Massi spent a huge amount of effort in
> configuring the editor and cleaning up the mess. My company didn't and
> ended up with sometimes literally every word in a sentence using a
> different font size or style. They gave up on html + cke pretty soon,
> but couldn't be convinced that this was a bad idea upfront.)
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.
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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-23 12:02 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 [this message]
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
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=C5DF8B60-BCB3-4E5F-A22A-0FA3B4124C46@fiee.net \
--to=texml@fiee.net \
--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).