################################################################################
#
# Project     : UDO manual
# Chapter     : Formats: Linuxdoc-SGML
# Language    : English
# Initial Date: 2009-06-05
# Author      : Dirk Hagedorn
# Co-author(s): Ulf Dunkel (fd)
# Write-access: fd
#
# ------------------------------------------------------------------------------
# 
# History
# -------
# 2009:
#   fd  Jun 05: file introduced (extracted from formats.ui)
#   fd  Jun 10: using macro (!file [])
#   fd  Jun 10: using macro (!code [])
#   fd  Jun 10: using EXAMPLE_... macros
# 2010:
#   fd  Mar 07: macro usage adjusted
#   fd  May 21: "&Aring;" uses an invisible hyphen (!-) to avoid replacement in HTML
#
################################################################################

!begin_node Linuxdoc-SGML
!html_name format_ldoc

In March 1996, Dirk Hagedorn found an article about Linuxdoc-SGML in the German Unix magazine ""iX"". 
It took two hours to download the Linuxdoc-SGML archive and
to implement this format into UDO. Unfortunately he didn't own a Linux
computer and so he wasn't able to test UDO's output.

Linuxdoc-SGML is a multiformat converter like UDO. With Linuxdoc-SGML you
can convert SGML files into (!LaTeX), RTF, HTML, Texinfo and manpages. But
it is not a lie to claim that UDO is more powerful than Linuxdoc-SGML 1.5.

!begin_description !not_compressed

##################################################

!item [The xlist environment is handled like a description environment!?]
Linuxdoc-SGML doesn't offer an environment like UDO's xlist environment. So
UDO is forced to handle it like a description environment.

##################################################

!ifdest [tex,pdf]
!item [Linuxdoc-SGML doesn't know (!T)&Aring;(!t), why?]
!else
!item [Linuxdoc-SGML doesn't know (!V)&Aring;(!v), why?]
!endif
Add the following line to (!file [/usr/lib/linuxdoc-sgml/rep/html/general]):

!begin_quote
!begin_verbatim
<!entity Aring sdata "&Aring;" >
!end_verbatim
!end_quote

##################################################

!end_description

!end_node
