<br><br><div class="gmail_quote">On Thu, Jul 28, 2011 at 2:10 AM, Ulrike Fischer <span dir="ltr"><<a href="mailto:news3@nililand.de">news3@nililand.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Am Thu, 28 Jul 2011 01:24:04 -0700 schrieb Johannes Wilm:<br>
<div class="im"><br>
<br>
>>> What I wonder though is what the state of the HTML that is being output<br>
>>> really is. It seems to me specifically that:<br>
<br>
>>> a. almost none of the <p>-tags are closed<br>
<br>
>> Use the xhtml-Option I mentioned earlier.<br>
<br>
> Ah, yes that's probably what I should done to start out with. Now when I<br>
> switch html for xhtml, it somehow breaks my SVG-fixing script. I didn't know<br>
> that the html-option would produce partially invalid HTML, as it seems.<br>
<br>
</div>It doesn't produce invalid html, it produce html 4.01:<br>
<br>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"<br>
<br>
Which is different to xhtml which would get with the xhtml option<br>
<br>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br>
<div class="im"><br>
<br>
>>> b. an element that is used a lot are "tspans" which the W3C validation<br>
>>> claims to not have heard about.<br>
<br>
</div><a href="http://www.w3.org/TR/SVG/text.html#TSpanElement" target="_blank">http://www.w3.org/TR/SVG/text.html#TSpanElement</a><br>
<div class="im"><br>
> I guess everything is currently changing, like<br>
<br>
> bibtex -> biblatex<br>
<br>
</div>bibtex is an application and biblatex a package.<br><div><br>
</div></blockquote><div> <br>Yes, I am aware of that. I translated som biblatex stuff a while back.
Still, it is a change that needs to be implemented various places --
such as LyX, such as tex4ht, such as in any bibtex-database
administration program.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
The transition is more<br>
<br>
bibtex + natbib or bibtex + jurabib or bibtex + some bib-style -><br>
bibtex + biblatex or biber + biblatex.<br>
<div class="im"><br>
> pdftex -> luatex<br>
> 8 bit -> utf-8<br>
> PDF -> EPUB<br>
<br>
</div>these are formats for very different purposes. pdf is a page<br>
description format, while in ebook/web-formats text can be easily<br>
refloated.<br></blockquote><div></div></blockquote><div> <br>I know. It's still an issue though that needs to be dealt with and is therefore a cause of problems with getting everything to work together.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
> PNG -> SVG<br>
<br>
PNG is a bitmap format, SVG a vector format. How would convert a<br>
foto to a vector format?<br></blockquote></blockquote><div><br>I am just saying that this is a period when some thing which previously were in PNG henceforth will be in SVG. The issues with that are that the Tikz -> SVg doesn't work perfectly yet, and apparently although SVG is part of the epub-specification, most epub-readers have bad or no SVg-renderers built in. This is yet another cause for issues I ended up writing a bunch of scripts that would fix the SVG-files, and in the end I made it convert the SVGs to PNGs and change the corresponding parts in the HTML-files. Not really all that smooth.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
> Kile -> LyX<br>
<br>
I will certainly never use LyX, and I don't any TeX/LaTeX/context<br>
expert who considers such a step.<br></blockquote></blockquote><div><br>Yeah, well I wrote for ages in Kile. Yet I need to communicate with the world around me. Professors can not really be trained to use anything else than Word. proofreaders (mine at least) I have managed to move onto LyX/Dropbox. And that was a challenge. When editing a student journal together with others, I can either choose (as I have in the past), that all the other editors send me the articles in Word-format, which I then convert to Latex by hand, whereupon for about 4 months I receive about 15 emails a day with some 20+ instructions in each of the type "On page 382 in the very last paragraph, there is a comma missing. You'll see it when you read the paragraph."<br>
<br>Or, alternatively, I can force everybody else to write and maintain everything in LyX in a Dorpbox-folder, with me holding one central masterfile (in latex) and my monster-script to auto-build the various output formats. This is what I plan on doing for all future. I can live with the fact that I don't have as much control as I used to with Kile.<font color="#888888"><span style="color: rgb(0, 0, 0);"> LyX rally only recently has become easy enough to install and usable for novices that I find it safe to try to do this.</span><br>
<br><font color="#000000">Anyways, it doesn't really matter. I was just rationalizing how the current state of the one and only state-of-the-art open source publishing software is what it is.</font><br><br></font></div>
</div>-- <br>Johannes Wilm<br><a href="http://www.johanneswilm.org" target="_blank">http://www.johanneswilm.org</a><br>tel: +1 (520) 399 8880<br><div style="display:inline"></div><br>