I not only enjoyed the slides content from D. Walter's and Andrei's talk, I also liked the visual design.  It looks like it was done with latex beamer? If so, can anyone tell me what theme was used, or maybe a pointer to the source code for the slides?

Neal Becker wrote:
> I not only enjoyed the slides content from D. Walter's and Andrei's talk, I
> also liked the visual design.  It looks like it was done with latex beamer? If so, can anyone tell me what theme was used, or maybe a pointer to the
> source code for the slides?

I prepared the initial raw text, and Andrei expanded on it and then used latex to produce the finished presentation. I like the results a lot, too, and am in the process of learning latex myself so I can do a better job with my own presentations.

I'll try and dig up the .tex file.

Reply to Walter,

> Neal Becker wrote:
> 
>> I not only enjoyed the slides content from D. Walter's and Andrei's
>> talk, I also liked the visual design.  It looks like it was done with
>> latex beamer? If so, can anyone tell me what theme was used, or maybe
>> a pointer to the source code for the slides?
>> 
> I prepared the initial raw text, and Andrei expanded on it and then
> used latex to produce the finished presentation. I like the results a
> lot, too, and am in the process of learning latex myself so I can do a
> better job with my own presentations.
> 
> I'll try and dig up the .tex file.
> 

Any chance this could be a excuse for getting the D ddoc stuff in a format that can be converted to .tex? The only major issue there is that it has lots of HTML tag hard coded in.

One minor issue is that there is no way (that I knwon of) to get dmd to generate multiple ddoc output files with anything but the default extension.

BCS wrote:
> Any chance this could be a excuse for getting the D ddoc stuff in a format that can be converted to .tex? The only major issue there is that it has lots of HTML tag hard coded in.

One of my goals is to get Ddoc to generate .tex output as well as html. What's stood in the way is I don't know latex, but that's changing.

Reply to Walter,

> BCS wrote:
> 
>> Any chance this could be a excuse for getting the D ddoc stuff in a
>> format that can be converted to .tex? The only major issue there is
>> that it has lots of HTML tag hard coded in.
>> 
> One of my goals is to get Ddoc to generate .tex output as well as
> html. What's stood in the way is I don't know latex, but that's
> changing.
> 

sweet!! Please do make the .ddoc -> tex macros part of the default install

Walter Bright wrote:
> BCS wrote:
>> Any chance this could be a excuse for getting the D ddoc stuff in a format that can be converted to .tex? The only major issue there is that it has lots of HTML tag hard coded in.
> 
> One of my goals is to get Ddoc to generate .tex output as well as html. What's stood in the way is I don't know latex, but that's changing.

Isn't Ddoc already prepared for generating non-HTML documentation, because of macros?

Reply to Ary,

> Walter Bright wrote:
> 
>> BCS wrote:
>> 
>>> Any chance this could be a excuse for getting the D ddoc stuff in a
>>> format that can be converted to .tex? The only major issue there is
>>> that it has lots of HTML tag hard coded in.
>>> 
>> One of my goals is to get Ddoc to generate .tex output as well as
>> html. What's stood in the way is I don't know latex, but that's
>> changing.
>> 
> Isn't Ddoc already prepared for generating non-HTML documentation,
> because of macros?
> 

yes, but Walter doesn't have the D docs set up to generate anything but HTML.

BCS wrote:
> Reply to Ary,
> 
>> Walter Bright wrote:
>>
>>> BCS wrote:
>>>
>>>> Any chance this could be a excuse for getting the D ddoc stuff in a
>>>> format that can be converted to .tex? The only major issue there is
>>>> that it has lots of HTML tag hard coded in.
>>>>
>>> One of my goals is to get Ddoc to generate .tex output as well as
>>> html. What's stood in the way is I don't know latex, but that's
>>> changing.
>>>
>> Isn't Ddoc already prepared for generating non-HTML documentation,
>> because of macros?
>>
> 
> yes, but Walter doesn't have the D docs set up to generate anything but HTML.

Oh, I see. Phobo's Ddoc is using HTML instead of macros... no?

Reply to Ary,

> BCS wrote:
> 
>> Reply to Ary,
>> 
>>> Walter Bright wrote:
>>> 
>>>> BCS wrote:
>>>> 
>>>>> Any chance this could be a excuse for getting the D ddoc stuff in
>>>>> a format that can be converted to .tex? The only major issue there
>>>>> is that it has lots of HTML tag hard coded in.
>>>>> 
>>>> One of my goals is to get Ddoc to generate .tex output as well as
>>>> html. What's stood in the way is I don't know latex, but that's
>>>> changing.
>>>> 
>>> Isn't Ddoc already prepared for generating non-HTML documentation,
>>> because of macros?
>>> 
>> yes, but Walter doesn't have the D docs set up to generate anything
>> but HTML.
>> 
> Oh, I see. Phobo's Ddoc is using HTML instead of macros... no?
> 

Phobo's Ddoc is using HTML _AND_ macros. (it was HTML to start with and has slowly been turning into macros)

Dnia Thu, 30 Aug 2007 11:08:47 -0700
Walter Bright <newshound1@digitalmars.com> napisał/a:

> BCS wrote:
> > Any chance this could be a excuse for getting the D ddoc stuff in a format that can be converted to .tex? The only major issue there is that it has lots of HTML tag hard coded in.
> 
> One of my goals is to get Ddoc to generate .tex output as well as html. What's stood in the way is I don't know latex, but that's changing.

BTW. i have working macros for unix manpages (groff)

http://smp.if.uj.edu.pl/~baryluk/d/ddoc-man/

groff_man.ddoc   - macros
test.sh  - small postprocessing. ddoc produces lots of white spaces :/
           and i have no idea how to disable them there and
           force them in othere places

License: Public Domain


i have also macros for latex, but they are more awfull :D

-- 
Witold Baryluk, aleph0
MAIL: baryluk@smp.if.uj.edu.pl
JID: movax@jabber.autocom.pl