LaTeX is not a word processor, it is a professional typesetting tool.
I see all the reasons to keep the docs in LaTex (like keeping the
process efficient at the moment), but this sentence here about
professional tools is probably not that serious as I read it, right ?
I don't know how you
Am 14.09.11 08:58, schrieb thorsten.i.r...@jyu.fi:
LaTeX is not a word processor, it is a professional typesetting tool.
I see all the reasons to keep the docs in LaTex (like keeping the
process efficient at the moment), but this sentence here about
professional tools is probably not that
On Tue, 2011-09-13 at 11:46 +0300, thorsten.i.r...@jyu.fi wrote:
LaTeX is not a word processor, it is a professional typesetting tool. I
don't know about fiction books, but the vast majority of science books you
can buy is done with LaTeX. If you know how to work with it (rather than
against
On Wed, Sep 14, 2011 at 10:31 AM, Jörg Emmerich wrote:
1) Writer, Poet, Engineering, Marketing, etc.
Most of those surely do not want to be bothered with the final looks of
their design - but surely some do (and then run into problems).
(I think the Marketing person here is part of the second
Thanks for the info - that confirms what I noticed: After Installing and
doing some tests with LaTex and LyX I did not find a feasible way to
import the newly designed appearance - seems you really have to just
extract everything except the plain text and and build it up new -
without the
Am 13.09.11 10:46, schrieb thorsten.i.r...@jyu.fi:
LaTeX is not a word processor, it is a professional typesetting tool.
I see all the reasons to keep the docs in LaTex (like keeping the
process efficient at the moment), but this sentence here about
professional tools is probably not that
Hi Joerg, Stuart, others,
I'll just add a few ideas, as most of the relevant stuff has already
been said.
Jörg Emmerich wrote:
joacher@gm.. now proposed the link to www.lyx.org and I had a short
look:
- seems you can even import HTML into that system
Personally I doubt that importing HTML is
Agreed ! In fact, it's up to everyone here to create and submit better
images, screenshots. Basically this is a the communit gets what they
deserve-situation ;-)
Quick note: I'd be happy to provide some high quality screenshots if desired.
Just let me know what kind of images are
Durk Talsma wrote:
[...] I have a huge surplus of images left over from generating material
for the official gallery, [...]
I know - yet I'd dare to note that illustrating a manual is slightly
different from just dropping a few nice images here and there ;-)
Thus, if someone has an eye for
Hi Martin
as you probably have seen, I am eager to help in supporting the update
of the Manual. Please see some questions to your remarks:
On Mon, 2011-09-12 at 10:33 +, Martin Spott wrote:
Personally I doubt that importing HTML is worth the effort, and I'll
try to let you know, why :-)
Hi Stuart
Thanks - that offer was a nice surprise
Surely I want to work together with all of you to get the best, up to
date Manual/PDF possible. And surely I am highly interested in
integrating what I have into any company-wide release system.
joacher@gm.. now proposed the link to www.lyx.org
Am Sat, 10 Sep 2011 10:18:27 +0200
schrieb Jörg Emmerich j-emmer...@online.de:
Well - yes - I am rather disappointed
That is not surprising!
Technically seen, it is correct that Latex is the most flexible format,
from which you can derive most other types, but that doesn't lessen the
nice
On Mon, Sep 5, 2011 at 2:45 PM, I wrote:
More comments when I get the time once I'm back.
Hi Jomo,
I finally got the time to look at your work in detail. I think there's
a lot of really good work here, and it obviously represents a lot of
time and effort. Thanks again.
I _really_ like a number
Jörg Emmerich wrote:
1) I am sure that most of our customers/users today rather read/search
online in a WIKI and/or Forum - but I also see that some people still
prefer a hardcopy to study.
From my perspective the difference between a Wiki and a Manual is not
so much about the format of
On 6 Sep 2011, at 09:12, Jörg Emmerich wrote:
Thank you both very much for your interest and encouragement
No problem. It is great that someone is interested in the docs. Unfortunately I
think you could have saved yourself a lot of effort if you'd posted 6 months
ago :(
As you'll see from my
Emmerich.. maybe we need a new documentation plan.. so u start it in your
mother tounge.. I thinks this agood idea as your have a determined mind
and idea
I think the best way is to write paragraphs in plain text and later we can
all convert...
This is better than tryiing to update the
On 1 Sep 2011, at 08:37, Jörg Emmerich wrote:
I wanted to introduce that outcome about end of this month to the
dev-team, to see especially whether the Originators of the getstart
still find their share in what I did, and concur to this change. I hope
nobody feels offended by my partly drastic
anyone looked at docbook. It would solve the problem.. but its a horrible to
use.. but there again that was with my experience a few years ago doing a
major update to smarty.php (had to it as my team was using it and was paid
as thus by my boss)
I certainly think that a html5/xml approach is cool
Hi Jörg! I only checked the English manual and did not read it thoroughly (way
too much text. I got my (aerospace engineering!) study books last
week and I decided that I should save my eyes/mind for the millions of pages
(those books are way too heavy!) that I'll have to read the
upcoming
Jörg wrote
Curtis
actually your question hits me about 1 month too early!
I am in the midst of a final checkout of my proposal for a newly styled
getstart. But you asked now - so I guess I ask everyone if my proposal
could be seen as what you are asking for. Pls have a look at
Am 01.09.11 10:24, schrieb Vivian Meazza:
Spelling the title correctly in the English version would be a huge
improvement.
Vivian
Hi Jörg
I hope Vivians English style is not the only feedback you get about your
work here. Your contribution is welcome, at lest for me, and maybe
others can
Curtis Olson wrote:
I get quite a few questions from people who fire up FlightGear for the first
time and have little aviation experience and zero prior FlightGear
experience. They need really basic help, like how do you start the engine.
I think you're looking for a concise manual :-)
22 matches
Mail list logo
