On Sat, 2011-12-10 at 10:17 -0700, Craig White wrote:
On Sat, 2011-12-10 at 13:57 +0100, NOSpaze wrote:
On Sat, 2011-12-10 at 20:50 +0800, Ed Greshko wrote:
On 12/10/2011 08:34 PM, Craig White wrote:
is there any doubt who this NOSpaze is?
Rodolfo Alcazar Portillo
Why do you ask?
Yea thats me, why do you ask? are you my neighbor?
----
I was wrong... in that case, I will answer.
sgml has long been used for professional publishing ( see adobe
framemaker).
The idea is that you can use fast/simple editors such as vi or emacs and
put in your own markup tags and save the processing (ie, generate
toc/footnotes/end notes/appendix/etc.) for later.
Thanks for the suggestion. I'll read how to do a TOC, footnotes and
commenting/tagging paragraps, summarizing in vim. If you can suggest any
link, TIA. "your own markup tags"... I wouldn't use sgml/xml, but i'll
wait for any links on how to apply them effectively.
WYSIWYG is an obstacle to writing but is in fact an artifact of
publishing and in that case, you can merely concentrate on writing and
leave all of the stylizing until the writing is finished.
WYSIWYG "is an obstacle to writing"? Damn! I knew it! Tell it to the
LibreOffice team. They need to know it.
Seemed to me to be a more than adequate suggestion that you mocked.
I do really appreciate your help, just it sounded illogic. Sorry for
making fun. I live it.
:)
--
NOSpaze <nospaze@gmail.com>
Context
- Re: [Libreoffice] Writing a book w/F16? · NOSpaze
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.