I just started typesetting the D manual in Latex, which would give (at least some of us) a much better accessible document. But there's a pleed to Walter:

WALTER - PLEASE! Each time you update your online documentation, can you also post here info on which html files were changed? Although I have some HTML to LaTeX scripts, they're not perfect, I have to make a lot of amendments to the LaTeX file, and it would be much easier to just copy - paste than convert everything from scratch again. Without this info it will get outdated as the former PDF document :-)

ssuukk wrote:
> I just started typesetting the D manual in Latex, which would give (at least some of us) a much better accessible document. But there's a pleed to Walter:
> 
> WALTER - PLEASE! Each time you update your online documentation, can you also post here info on which html files were changed? Although I have some HTML to LaTeX scripts, they're not perfect, I have to make a lot of amendments to the LaTeX file, and it would be much easier to just copy - paste than convert everything from scratch again. Without this info it will get outdated as the former PDF document :-)

The documentation is released along with the compiler, so you could just diff it against previous versions.  Easy as pie.  (get cygwin if you don't have unix tools at your disposal: <http://cygwin.com>)

If you want to get really ambitious, you could write a script to transform and apply those diffs to the LaTeX source.

 -- andy

Andy Friesen wrote:
> 
> The documentation is released along with the compiler, so you could just diff it against previous versions.  Easy as pie.  (get cygwin if you don't have unix tools at your disposal: <http://cygwin.com>)
> 
> If you want to get really ambitious, you could write a script to transform and apply those diffs to the LaTeX source.
> 
UNLESS Walter doesn't add a new html file to directory structure, it will work...

Andy Friesen wrote:

>
> The documentation is released along with the compiler, so you could just diff it against previous versions.  Easy as pie.  (get cygwin if you don't have unix tools at your disposal: <http://cygwin.com>)

Or even just check the modification date.

>
> If you want to get really ambitious, you could write a script to transform and apply those diffs to the LaTeX source.
>
>  -- andy

ssuukk wrote:
> 
>> If you want to get really ambitious, you could write a script to transform and apply those diffs to the LaTeX source.
>>
> UNLESS Walter doesn't add a new html file to directory structure, it will work...
> 

Right, but that doesn't happen frequently enough to be a huge issue.

 -- andy

"ssuukk" <ssuukk@.go2.pl> wrote in message news:bugg1r$1285$1@digitaldaemon.com...
> I just started typesetting the D manual in Latex, which would give (at least some of us) a much better accessible document. But there's a pleed to Walter:
>
> WALTER - PLEASE! Each time you update your online documentation, can you also post here info on which html files were changed? Although I have some HTML to LaTeX scripts, they're not perfect, I have to make a lot of amendments to the LaTeX file, and it would be much easier to just copy - paste than convert everything from scratch again. Without this info it will get outdated as the former PDF document :-)

There are two ways to tell.
1) I keep the file creation time correct in the zip file, so just look at
the files with dates on them later than the last latex document.
2) I also embed the last modified date into the html files themselves, look
at the top of each page. Although this is less accurate, as sometimes I
forget to update it.

Walter wrote:

>2) I also embed the last modified date into the html files themselves, look
>at the top of each page. Although this is less accurate, as sometimes I
>forget to update it.
>
>  
>
In some HTML editors you can insert a special field that will automaticly update when you modify the document.

"J Anderson" <REMOVEanderson@badmama.com.au> wrote in message news:buhl83$2u73$1@digitaldaemon.com...
> Walter wrote:
>
> >2) I also embed the last modified date into the html files themselves,
look
> >at the top of each page. Although this is less accurate, as sometimes I forget to update it.
> >
> >
> >
> In some HTML editors you can insert a special field that will automaticly update when you modify the document.

I don't use an html editor, I use microemacs <g>.

>>
>>In some HTML editors you can insert a special field that will
>>automaticly update when you modify the document.
> 
> 
> I don't use an html editor, I use microemacs <g>.
> 
Unfortunately it shows: there are lots of unclosed tags, which make automatic translation of these pages real hell...

Can you/Walter try to use HTML Tidy utility to clean up the original html docs?

http://tidy.sourceforge.net/

BA


ssuukk wrote:
>>>
>>> In some HTML editors you can insert a special field that will
>>> automaticly update when you modify the document.
>>
>>
>>
>> I don't use an html editor, I use microemacs <g>.
>>
> Unfortunately it shows: there are lots of unclosed tags, which make automatic translation of these pages real hell...
>