On Friday June 20 2008 11:47, you wrote:
>There's a pretty good chance that TeX is going to become obsolete, and
>replaced by some HTML or XML derivative.  Many technical publishers
>have already made the transition.  See, for example, the following
> link from Cambridge University Press
>
> https://authornet.cambridge.org/information/productionguide/stm/XML_w
>orkflow.asp#xml_introduction

https://authornet.cambridge.org/information/productionguide/stm/LaTex_workflow.asp

Looks like they support LaTeX just fine. From that page, it even sounds 
like submitting in LaTeX will result in a a faster time to actual 
publication: "LaTeX workflows are generally speedier than the XML or 
conventional equivalents." I saw no evidence that LaTeX is being 
replaced by XML. I did note that they say the majority of books use 
XML, but i'm guessing more potential authors these days have a word 
processor that can spit out some form of XML than know how to write 
LaTeX.

Please note that i'm a bit biased though. For what few papers i have to 
write these days i use my favorite text editor to write LaTeX files. 
I've been using it for close to a decade. In that time i've found LaTeX 
has some similarties to OpenBSD. In either case, i've learned to trust 
that someone smarter than me (at least in the areas of page layout and 
Unix system administration) spent some time considering everything, and 
i should just use the default settings unless i have a legitimate 
reason for wanting to change them. In other words, don't turn the knobs 
just for the sake of turning them. By following that simple rule, it is 
quite fast and easy to write something in LaTeX, and the output is 
good. Similarly, setting up and using an OpenBSD system is fast and 
easy, and it just works.

------------------------------------------------------------------------
Dan Ramaley                            Dial Center 118, Drake University
Network Programmer/Analyst             2407 Carpenter Ave
+1 515 271-4540                        Des Moines IA 50311 USA

Reply via email to