@david_megginson I worked with #SGML at a publishing company in the late 1990's. I recall the Navy using it for documentation. There was only one other person in my local area I could find that worked with SGML.
I liked working in it but it was a niche job market.
[Перевод] Вся мощь открытого исходного кода в PostgreSQL
PostgreSQL — одна из самых популярных СУБД, и это во многом благодаря открытому исходному коду. В статье рассказывается о том, как открытость кода влияет на развитие PostgreSQL и создание сообщества вокруг неё.
https://habr.com/ru/companies/flant/articles/901622/
#open_source #postgresql #исходный_код #коммиты #commit #git #git_log #sgml #git_blame #source_code
Does anyone happen to have a copy of:
Floyd, Michael. A Conversation with Charles F. Goldfarb. Web Techniques (Vol.3, Issue 11), pp.38–41, November, 1998
It used to be online, but has now disappeared, and the Internet Archive doesn’t have it either. I’d like to check a quote that I copied back then.
Markup Languages, by @j9t [@frontenddogma.com]:
https://meiert.com/en/blog/markup-languages/
#overviews #linklists #sgml #html #xml #xhtml #hdml #dhtml #mathml #wml #chtml
Well, “Episode 21: Keynote — John McCarthy” actually has a recording and he gives that quote at timestamp 1:13:15:
http://www.oopsla.org/oopsla2007/index56d8.html
http://www.oopsla.org/podcasts/Keynote_JohnMcCarthy.mp3
“When W3C decided not to use #LISP format but to imitate #SGML for that [it] showed a certain capacity to make mistakes” *laughter* “which they probably hadn't lost”
Conclusion: the first part is similar, but the second part of the original quote is unfamiliar.
Isn't the WWW a wonderful to be able to research this? #markupLanguages
@david_megginson @HugoHeagren Currently, I use https://github.com/docbook/xslTNG which depends on the open source home edition of saxon XSLT processor to convert DocBook XML to HTML/ePub, and use #CSS based publishing softwares like https://vivliostyle.org or https://www.princexml.com/
There are zero actively maintained/usable on modern computers #SGML or #DSSSL processors known to me.
El 28 de octubre de 1969, se presenta el SGML (Standard Generalized Markup Language) por la ANSI. El SGML es el precursor del HTML moderno
#retrocomputingmx #SGML
fwiw, I used #DocBook #SGML in #Emacs to generate LaTeX/LilyPond, even when Macmillan demanded I submit MSWord¹ docs, I'd just emit them as an output! Mind you, that was last century, but I'd still do it that way today, if I had to.
___
¹ I call those apps "font painters', or WYSIAYG (what you see is ALL you get
SHORTTAG syntax in SGML kinda reminds of Pug (et al.) which I love.
```
<title/Misinterpreted/
<p/Little-known SGML markup features/
```
Ejemplo de la necesidad de marcas <verse> en html.
https://masto.es/@machadobot/112631949793897660
En poesía española, un verso puede continuar en párrafo o personaje distinto.
La iniciativa #TEI de #SGML incluía marcas <verse>, pero al hacer el "html semántico" (xhtml) se olvidó todo lo que los especialistas en lengua y literatura habían ido encontrando. El html/css es tan poco semántico como el #html 1.0.(+)
@callionica HTML before 4.0 was defined with SGML which gives it the flexibility of auto closing tags, but I doubt any #SGML / #DSSSL implementation is still useable today and if people would still be willing to learn it after the language specification has been stale for a while
As I possibly need to do soon something with #DITA.
DITA which is based on XML with some DTD is as like as HTML derived from SGML. In fact HTML is a simplified SGML.
I was aware that #SGML was developed at Boing. They invented it for Airplane documentation.
Today I learned that SGML is based on GML: "General Markup Language" from IBM.
But maybe simply "Golfarb, Mosher, Lorie": the #IBM engineers back in the 1960s.
This actually sounds like a good use case for #SGML. I'm pretty sure you could define all, or at least most, of Markdown syntax using the SHORTREF feature. From there you could add any additional metadata tags (possibly with their own custom SHORTREF syntax) you want into the grammar
SGML is a bit of a beast however, it can be daunting to get started with it... :blobfoxthink:
What’s especially interesting is that Don Chamberlin isn’t just some random IBMer (https://en.wikipedia.org/wiki/Donald_D._Chamberlin). And he wasn’t only involved with Quill SGML editor, but also with the Quilt XML query language, which heavily influenced XQuery (he was one of the editors of the W3C XQuery 1.0 recommendation).
#XMLPrague #REXX #SGML #HistoryOfComputing #DocumentEngineering
In my talk for the 2019 #XMLPrague paper “History and the Future of Markup” http://archive.xmlprague.cz/2019/files/xmlprague-2019-proceedings.pdf#page=335 I speculated about the use of #REXX as a language for #SGML tree manipulation.
Last night I “discovered” that REXX had indeed been used for this at IBM, and Goldfarb knew about it: namely in the experimental Quill editor running on an experimental windowing system on an experimental operating system on the IBM RT PC… (see, e.g., https://doi.org/10.1145/62506.62524)
From: "Didier PH Martin" <martind@n...>
To: "'XML Dev'" <xml-dev@i...>
Date: Thu, 11 Mar 1999 15:01:41 -0500
RE: Namespaces and DTDs
HI Bill,
<YourComment>
Lisp and XML have a few things in common, like being easy to
determine if they are well formed. Frankly, I think XML will be
better in the long run because it can be validated against various
schema.
</YourComment>
<Reply>
I am not sure of that.
a) a Lisp document could be made SGML compliant because SGML can let you
define begin and end tag's delimiters (Ex: dsssl).
[…]
Can we take JSON as #SGML compliant? real question, im boutta be lookin into