News for hackers. Stuff that matters.
Re:Compare AsciiDoc and Markdown by rm445 on Tuesday July 06, 2021 @06:05AM (#27746230)
It does tend to make one worry that all the tools will be hideously un-unicode aware and mangle any non-ASCII documents.

I would like to imagine that in this day and age that isn't the case, but the name works against it.

Re:Compare AsciiDoc and Markdown by oneeyedpigeon on Tuesday July 06, 2021 @06:22AM (#27746369)
Particularly when the syntax bakes in things like support for converting certain ASCII sequences into Unicode characters [0]

[0] https://docs.asciidoctor.org/asciidoc/latest/text/quotation-...

Re:Compare AsciiDoc and Markdown by bloak on Tuesday July 06, 2021 @07:13AM (#27746792)
Yes, I finally got around to adding some "quail" stuff to my .emacs so that I can directly type various kinds of quotation mark and dash rather than rely on complex conversion rules that sometimes go wrong.

The lack of first-class support for balanced quotation marks seems to be a major problem for computers. I think a lot of computer code, particularly scripts, would be easier to read and less buggy if the languages had been designed by someone with balanced quotation marks on their keyboard.

As a thought experiment, imagine what Lisp would look like if '(' and ')' were the same character and you had to use the same work-arounds that shell scripts use for open quotation mark and close quotation mark being the same character. Instead of (a ((b c) d)) we'd write |a \|\\\|b c\\\| d\||. That's fine, right? We can live with that?

Perhaps we should think ourselves lucky that 0 and O are not the same character, and 1 and l, like they were on the first mechanical typewriters.

Mind you, there's one similar annoyance that predates typewriters and continues to plague us in Unicode: apostrophe and closing single quotation mark are logically quite different things, but they're the same character: ’

Re:Compare AsciiDoc and Markdown by enriquto on Tuesday July 06, 2021 @09:52AM (#27748533)
> Yes, I finally got around to adding some "quail" stuff to my .emacs

Why into .emacs and not into the global keyboard configuration? Don't you ever write text outside of emacs?

Re:Compare AsciiDoc and Markdown by bloak on Tuesday July 06, 2021 @11:00AM (#27749522)
Yes, good question. One reason is that I haven't found a convenient portable way of modifying Linux keyboard configurations. Another is that sometimes I'm SSH-ing in from a machine that isn't even Linux.

I have used xkbcomp to replace a character I don't need with one I do, but the recipe tends to require maintenance and I don't know how to program dead keys with that approach. Perhaps there's a better way nowadays.

Re:Compare AsciiDoc and Markdown by enriquto on Tuesday July 06, 2021 @11:45AM (#27750066)
I was somehow expecting the answer to be: "Yes, I do all my keyboard input from inside emacs, including running the shell".

For linux-portable keyboard configuration, you may find that an unholy mix of setxbmap (to set up the grand options) and xmodmap (to modify a few particular keys) is what works best for you. At least it does for me.

> sometimes I'm SSH-ing in from a machine that isn't even Linux.

ah! the horror!

Re:Compare AsciiDoc and Markdown by joshspankit on Tuesday July 06, 2021 @07:12AM (#27746787)
Came here to say this. UTF-8/16 represents such a relief from the previous text-encoding nightmares that I run away from any tooling that does not use it.

If anyone else was a web dev in the 90s, you know what I’m talking about.

Re:Compare AsciiDoc and Markdown by MattBlissett on Tuesday July 06, 2021 @07:38AM (#27747041)
AsciiDoctor supports Unicode just fine.

We've integrated it with PO4A[0] and CrowdIn.com to support a translation workflow, and so far have one document in Chinese: [1].

Another (tiny) example is [2] with an emoji star, you can "Edit this page" and see the Unicode source.

[0] https://po4a.org/

[1] https://docs.gbif.org/collections-idea-paper/zh/

[2] https://ipt.gbif.org/manual/en/ipt/2.5/data-hosting-centres#...

Re:Compare AsciiDoc and Markdown by SAI_Peregrinus on Tuesday July 06, 2021 @01:37PM (#27751776)
The issue is that the name strongly implies that it doesn't. If a system is named "Doesn'tSupportImportantThingSys" don't be surprised when people don't bother to check the documentation to find that it actually does support the important thing. They'll just skip it.
Re:Compare AsciiDoc and Markdown by joshspankit on Wednesday July 07, 2021 @09:09PM (#27767499)
^ this.

ASCII is so old that I picture ANSI colour blocks as it’s successor, and both of those are firmly in the “nightmarish text encoding days”