On Thu, 19 Apr 2001, Tatsuo Ishii wrote:
It actually was pretty quick. The fixes were more cleaning up strange
conversion from HTML to LaTeX.
Looks nice, but I'm afraid I have to do all the work above for 489
HTML files:-)
It's not all that bad. There's really only 486, the other three
Tatsuo Ishii writes:
Sorry you are seeing trouble. I missed seeing your traffic on the dsssl
list to which I am subscribed; which one are you using?
[EMAIL PROTECTED]
The mailing list you should be on is [EMAIL PROTECTED]
(see http://lists.oasis-open.org), which is more about docbook
Sorry you are seeing trouble. I missed seeing your traffic on the dsssl
list to which I am subscribed; which one are you using?
[EMAIL PROTECTED]
The mailing list you should be on is [EMAIL PROTECTED]
(see http://lists.oasis-open.org), which is more about docbook processing
and less
Sorry you are seeing trouble. I missed seeing your traffic on the dsssl
list to which I am subscribed; which one are you using?
[EMAIL PROTECTED]
The mailing list you should be on is [EMAIL PROTECTED]
(see http://lists.oasis-open.org), which is more about docbook processing
and
Perhaps I'm stuck in the eighties when I did my thesis in LaTeX, but
I was of the impression that what's considered good style in LaTeX *is*
content-based markup. Sure, a LaTeXer may occasionally be forced to
throw in low-level stuff like a \pagebreak to get nice looking results
... but I
Thomas Lockhart [EMAIL PROTECTED] writes:
This is a step forward?
Not true. If you embed pagebreak commands *in the source* then those
breaks *must* be reevaluated every time the docs change. If content is
added or removed, the appropriate place for a page break will likely
change, so
5) We have been working for translating docs into Japanese using
EUC_JP encoding. Converting to HTML is no problem, but we cannot
get correct results for sgml- RTF conversion at all. The
translated docs are just not be able to read, showing random
characters. It seems that
Bruce Momjian writes:
However, what it doesn't give you is much control over
appearance except how to map the tags to appearance. You can't tweek
appearance in SGML unless you make special tags for certain appearances.
How do you derive this conclusion? SGML gives you a boatload of ways to
Bruce Momjian writes:
However, what it doesn't give you is much control over
appearance except how to map the tags to appearance. You can't tweek
appearance in SGML unless you make special tags for certain appearances.
How do you derive this conclusion? SGML gives you a boatload of
Tatsuo, when I added SGML reference pages to the back of my book, I took
the HTML-generated output from SGML and loaded that into LaTeX. I did
have to do a few things:
convert SGML to HTML
html2latex
add * to \subsection* ?
remove \newline
remove
It actually was pretty quick. The fixes were more cleaning up strange
conversion from HTML to LaTeX.
Looks nice, but I'm afraid I have to do all the work above for 489
HTML files:-)
What I'm doing now is trying to fix openjade. It is written in C++,
and I hate C++, no way...
I
My feedback at this time is mostly the desire to know a bit better
what prevents the hardcopy docs from being built automatically. I am
currently having some trouble compiling jadetex, so I can't take a
look at the generated PDF yet, but I assume there's something wrong
with it. That seems
Thomas Lockhart [EMAIL PROTECTED] writes:
3) Page breaks are not always ideal. Some hand adjustments are desirable
to get a better flow to the docs, especially wrt examples and lists; you
don't want them breaking between pages if you can avoid it, especially
with short examples.
This
Tom Lane writes:
It seems to me that all of the other problems you enumerate are simply
bugs in the doc toolchain. We've worked around them rather than tried
to fix them because that was the shortest path to a result, but if Chris
wants to tackle actually fixing them, that would sure be
It seems to me that all of the other problems you enumerate are simply
bugs in the doc toolchain. We've worked around them rather than tried
to fix them because that was the shortest path to a result, but if Chris
wants to tackle actually fixing them, that would sure be nice. Based on
your
Hmm. Actually, afaik we were the first large open source project to
successfully use the jade toolset for docs. Others have used our project
as an example to help get them going, since as you have already found
out getting the tool chain completely set up is not trivial.
There are at least
5) We have been working for translating docs into Japanese using
EUC_JP encoding. Converting to HTML is no problem, but we cannot
get correct results for sgml- RTF conversion at all. The
translated docs are just not be able to read, showing random
characters. It seems that
Thomas Lockhart [EMAIL PROTECTED] writes:
There is a difference between using techniques which markup content
(DocBook, XML, etc) as opposed to those which markup appearence (latex).
Perhaps I'm stuck in the eighties when I did my thesis in LaTeX, but
I was of the impression that what's
They're not ready yet.
Since they were deemed non-essential for this release, and since the
release schedule is not built around their creation, I no longer feel
obligated to have them finished on the release date. A nice change from
the deadlines I've been working on for the last three years
On Tue, Apr 17, 2001 at 12:07:26AM +, Thomas Lockhart wrote:
They're not ready yet.
Since they were deemed non-essential for this release, and since the
release schedule is not built around their creation, I no longer feel
obligated to have them finished on the release date. A nice
20 matches
Mail list logo
