www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - PDF spec

reply Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
There's quite a bit of work left to do, but the PDF spec already has 386 
pages of goodness and starts to look seriously cool. Take a peek!

http://dlang.org/dlangspec.pdf

(still subject to http://d.puremagic.com/issues/show_bug.cgi?id=9369, so 
don't mind the absent underscores here and there)


Andrei
Jan 23 2013
next sibling parent reply Walter Bright <newshound2 digitalmars.com> writes:
On 1/23/2013 10:26 PM, Andrei Alexandrescu wrote:

 There's quite a bit of work left to do, but the PDF spec already has 386 pages
 of goodness and starts to look seriously cool. Take a peek!

 http://dlang.org/dlangspec.pdf


Awesome progress!

I think pdf allows for clickable links. Do you think those would be a good
idea? 
I did make them work in the ebook version.
Jan 23 2013
parent reply Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 1/24/13 1:33 AM, Walter Bright wrote:

 On 1/23/2013 10:26 PM, Andrei Alexandrescu wrote:

 There's quite a bit of work left to do, but the PDF spec already has
 386 pages
 of goodness and starts to look seriously cool. Take a peek!

 http://dlang.org/dlangspec.pdf


 Awesome progress!

 I think pdf allows for clickable links. Do you think those would be a
 good idea? I did make them work in the ebook version.


Yes, it does, and I even think I use it in a few places. But I haven't 
pursued links systematically yet.

Andrei
Jan 23 2013
next sibling parent Jacob Carlborg <doob me.com> writes:
On 2013-01-24 07:36, Andrei Alexandrescu wrote:


 Yes, it does, and I even think I use it in a few places. But I haven't
 pursued links systematically yet.


It does have links, in the table of contents. But they don't work. The 
external links seems to work.

-- 
/Jacob Carlborg
Jan 23 2013
prev sibling parent reply "kiskami" <kiskami freemail.hu> writes:
On Thursday, 24 January 2013 at 06:36:17 UTC, Andrei Alexandrescu 
wrote:

 I think pdf allows for clickable links. Do you think those 
 would be a
 good idea? I did make them work in the ebook version.


 Yes, it does, and I even think I use it in a few places. But I 
 haven't pursued links systematically yet.

 Andrei


Just my 2c:
The - in windows\bin resident - d.chm is very good for using as a 
reference, because you have a linked TOC, text and keyword search 
and bookmarks capability all the time on the left.

IMHO the pdf format is more suited for printing or maybe reading 
on ebook readers, but it would be definitely userfriendlier to 
have the TOC links on the bookmarks tab in Acrobat Reader. :)
Jan 24 2013
next sibling parent reply Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 1/24/13 3:20 AM, kiskami wrote:

 IMHO the pdf format is more suited for printing or maybe reading on
 ebook readers, but it would be definitely userfriendlier to have the TOC
 links on the bookmarks tab in Acrobat Reader. :)


Printing would be indeed the main target of the PDF.

Andrei
Jan 24 2013
parent Paulo Pinto <pjmlp progtools.org> writes:
Am 24.01.2013 17:25, schrieb Andrei Alexandrescu:

 On 1/24/13 3:20 AM, kiskami wrote:

 IMHO the pdf format is more suited for printing or maybe reading on
 ebook readers, but it would be definitely userfriendlier to have the TOC
 links on the bookmarks tab in Acrobat Reader. :)


 Printing would be indeed the main target of the PDF.

 Andrei


I rather spare some trees. :)
Jan 24 2013
prev sibling next sibling parent "SomeDude" <lovelydear mailmetrash.com> writes:
On Thursday, 24 January 2013 at 08:20:04 UTC, kiskami wrote:

 Just my 2c:
 The - in windows\bin resident - d.chm is very good for using as 
 a reference, because you have a linked TOC, text and keyword 
 search and bookmarks capability all the time on the left.

 IMHO the pdf format is more suited for printing or maybe 
 reading on ebook readers, but it would be definitely 
 userfriendlier to have the TOC links on the bookmarks tab in 
 Acrobat Reader. :)


I agree, the .chm format is extremely handy for searching and 
reference.
Jan 27 2013
prev sibling parent reply Jordi Sayol <g.sayol yahoo.es> writes:
Al 24/01/13 09:20, En/na kiskami ha escrit:

 The - in windows\bin resident - d.chm is very good for using as a reference,
because you have a linked TOC, text and keyword search and bookmarks capability
all the time on the left.


I've built a chm spec. check it out.
http://d-packages.googlecode.com/files/dlangspec.chm

-- 
Jordi Sayol
Jan 29 2013
parent reply "kiskami" <kiskami freemail.hu> writes:
On Wednesday, 30 January 2013 at 07:19:14 UTC, Jordi Sayol wrote:

 I've built a chm spec. check it out.
 http://d-packages.googlecode.com/files/dlangspec.chm


Something is wrong with this file - pages dont show up for me.
There's an (iexplorer?) error message, but its in my native 
language, so I can only guess the corresponding english 
translation. Its something like "the user aborted the page 
loading process". Page links are incorrect maybe? I dont use 
iexplorer, sorry. :)
Jan 30 2013
parent reply Paulo Pinto <pjmlp progtools.org> writes:
Am 30.01.2013 18:08, schrieb kiskami:

 On Wednesday, 30 January 2013 at 07:19:14 UTC, Jordi Sayol wrote:

 I've built a chm spec. check it out.
 http://d-packages.googlecode.com/files/dlangspec.chm


 Something is wrong with this file - pages dont show up for me.
 There's an (iexplorer?) error message, but its in my native language, so
 I can only guess the corresponding english translation. Its something
 like "the user aborted the page loading process". Page links are
 incorrect maybe? I dont use iexplorer, sorry. :)


Have you unblocked the file?

chm files can contain ActiveXs, so as security measure since the XP 
security overall you need to explicitly allow chm files that you 
downloaded to be secure.

Check the file properties.

--
Paulo
Jan 30 2013
parent reply "kiskami" <kiskami freemail.hu> writes:
On Wednesday, 30 January 2013 at 18:53:02 UTC, Paulo Pinto wrote:

 Have you unblocked the file?

 chm files can contain ActiveXs, so as security measure since 
 the XP security overall you need to explicitly allow chm files 
 that you downloaded to be secure.

 Check the file properties.


Thanks for the tip, it works now.

Im not a big fan of the light green background, but the chm is 
awesome otherwise! :)
Jan 31 2013
parent reply Jordi Sayol <g.sayol yahoo.es> writes:
Al 31/01/13 14:50, En/na kiskami ha escrit:

 On Wednesday, 30 January 2013 at 18:53:02 UTC, Paulo Pinto wrote:

 Have you unblocked the file?

 chm files can contain ActiveXs, so as security measure since the XP security
overall you need to explicitly allow chm files that you downloaded to be secure.

 Check the file properties.


 
 Thanks for the tip, it works now.
 
 Im not a big fan of the light green background, but the chm is awesome
otherwise! :)
 


What do you mean with "light green background"?

<http://twitpic.com/bzu2je/full>
-- 
Jordi Sayol
Jan 31 2013
parent reply "kiskami" <kiskami freemail.hu> writes:
On Thursday, 31 January 2013 at 19:47:37 UTC, Jordi Sayol wrote:

 What do you mean with "light green background"?

 <http://twitpic.com/bzu2je/full>


The background of the pages isn't white, but a light green color.

Its maybe nit-picking, but I just find the typography of the 
"Language Reference" on the home page much better.
Jan 31 2013
parent reply Jordi Sayol <g.sayol yahoo.es> writes:
Al 31/01/13 22:39, En/na kiskami ha escrit:

 On Thursday, 31 January 2013 at 19:47:37 UTC, Jordi Sayol wrote:

 What do you mean with "light green background"?

 <http://twitpic.com/bzu2je/full>


 
 The background of the pages isn't white, but a light green color.
 
 Its maybe nit-picking, but I just find the typography of the "Language
Reference" on the home page much better.
 


New chm with the typography of the "Language Reference" on the home page.
http://d-packages.googlecode.com/files/dlangspec-2.chm

-- 
Jordi Sayol
Jan 31 2013
parent reply "kiskami" <kiskami freemail.hu> writes:
On Thursday, 31 January 2013 at 22:54:58 UTC, Jordi Sayol wrote:

 New chm with the typography of the "Language Reference" on the 
 home page.
 http://d-packages.googlecode.com/files/dlangspec-2.chm


\o/
Ripping! :)
Jan 31 2013
parent reply Jordi Sayol <g.sayol yahoo.es> writes:
Al 01/02/13 01:27, En/na kiskami ha escrit:

 On Thursday, 31 January 2013 at 22:54:58 UTC, Jordi Sayol wrote:

 New chm with the typography of the "Language Reference" on the home page.
 http://d-packages.googlecode.com/files/dlangspec-2.chm


 
 \o/
 Ripping! :)
 


New CHM release
http://d-packages.googlecode.com/files/dlangspec.chm

-- 
Jordi Sayol
Feb 02 2013
parent reply "SomeDude" <lovelydear mailmetrash.com> writes:
On Saturday, 2 February 2013 at 19:44:20 UTC, Jordi Sayol wrote:

 Al 01/02/13 01:27, En/na kiskami ha escrit:

 On Thursday, 31 January 2013 at 22:54:58 UTC, Jordi Sayol 
 wrote:

 New chm with the typography of the "Language Reference" on 
 the home page.
 http://d-packages.googlecode.com/files/dlangspec-2.chm


 
 \o/
 Ripping! :)
 


 New CHM release
 http://d-packages.googlecode.com/files/dlangspec.chm


It's completely empty for me. Not a single page is showing.
Feb 02 2013
parent reply Jordi Sayol <g.sayol yahoo.es> writes:
Al 02/02/13 23:49, En/na SomeDude ha escrit:

 On Saturday, 2 February 2013 at 19:44:20 UTC, Jordi Sayol wrote:

 Al 01/02/13 01:27, En/na kiskami ha escrit:

 On Thursday, 31 January 2013 at 22:54:58 UTC, Jordi Sayol wrote:

 New chm with the typography of the "Language Reference" on the home page.
 http://d-packages.googlecode.com/files/dlangspec-2.chm


 \o/
 Ripping! :)


 New CHM release
 http://d-packages.googlecode.com/files/dlangspec.chm


 
 It's completely empty for me. Not a single page is showing.
 


No problem in w2k:
http://postimage.org/image/3ncruo83v/
and wXP:
http://postimage.org/image/628ddmczp/

-- 
Jordi Sayol
Feb 02 2013
parent "kiskami" <kiskami freemail.hu> writes:
On Saturday, 2 February 2013 at 23:38:54 UTC, Jordi Sayol wrote:

 No problem in w2k:
 http://postimage.org/image/3ncruo83v/
 and wXP:
 http://postimage.org/image/628ddmczp/


Working on Win7 64bit too.
Feb 02 2013
prev sibling next sibling parent reply Jacob Carlborg <doob me.com> writes:
On 2013-01-24 07:26, Andrei Alexandrescu wrote:

 There's quite a bit of work left to do, but the PDF spec already has 386
 pages of goodness and starts to look seriously cool. Take a peek!

 http://dlang.org/dlangspec.pdf

 (still subject to http://d.puremagic.com/issues/show_bug.cgi?id=9369, so
 don't mind the absent underscores here and there)


I know that this is that standard layout/theme of Latex but I don't 
understand why links need to looks so horrible. A red or cyan square 
around the text.

-- 
/Jacob Carlborg
Jan 24 2013
next sibling parent "H. S. Teoh" <hsteoh quickfur.ath.cx> writes:
On Thu, Jan 24, 2013 at 09:00:54AM +0100, Jacob Carlborg wrote:

 On 2013-01-24 07:26, Andrei Alexandrescu wrote:

There's quite a bit of work left to do, but the PDF spec already has
386 pages of goodness and starts to look seriously cool. Take a peek!

http://dlang.org/dlangspec.pdf

(still subject to http://d.puremagic.com/issues/show_bug.cgi?id=9369, so
don't mind the absent underscores here and there)


 
 I know that this is that standard layout/theme of Latex but I don't
 understand why links need to looks so horrible. A red or cyan square
 around the text.


[...]

Isn't this be configurable?


T

-- 
Жил-был король когда-то, при нём блоха жила.
Jan 24 2013
prev sibling parent reply Philippe Sigaud <philippe.sigaud gmail.com> writes:
On Thu, Jan 24, 2013 at 5:46 PM, H. S. Teoh <hsteoh quickfur.ath.cx> wrote:

 On Thu, Jan 24, 2013 at 09:00:54AM +0100, Jacob Carlborg wrote:



 I know that this is that standard layout/theme of Latex but I don't
 understand why links need to looks so horrible. A red or cyan square
 around the text.





 Isn't this be configurable?


Yes, it is. It's just the default for the hyperref package.

Here is what I use for my D template tutorial (here adapted for the spec)

\usepackage[pdftex]{hyperref}

\hypersetup{
    pdftitle={D Programming Language Specification},
    pdfauthor={D Team},
    pdfsubject={D Spec},
    pdfkeywords={D} {programming} {specification} {language} {grammar},
    colorlinks=true,
    linkcolor=red,
    urlcolor=darkblue
}

\begin{document}
...
Jan 24 2013
next sibling parent FG <home fgda.pl> writes:
On 2013-01-24 21:59, Philippe Sigaud wrote:

 I know that this is that standard layout/theme of Latex but I don't
 understand why links need to looks so horrible. A red or cyan square
 around the text.





 Isn't this be configurable?


 Yes, it is. It's just the default for the hyperref package.



Yeah, the colorlinks option is much better - boxes are distracting and should
be 
restricted to their main purpose... marking which authors have died. ;)

Other suggestion: a bit smaller margins, so the code won't wrap as much, and 
using footnotesize font in listings for same reason.

Now, tables - that's a PITA. I always end up in a cycle where I generate a PDF, 
preview it, tweak the tables (adjust column sizes, print the whole table in a 
small font, rotate the table or use a longtable), then generate the PDF again, 
and so on. I wonder how you approach this problem. Hints inside the 
documentation itself, perhaps?
Jan 24 2013
prev sibling parent reply Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 1/24/13 3:59 PM, Philippe Sigaud wrote:

 On Thu, Jan 24, 2013 at 5:46 PM, H. S. Teoh<hsteoh quickfur.ath.cx>  wrote:

 On Thu, Jan 24, 2013 at 09:00:54AM +0100, Jacob Carlborg wrote:



 I know that this is that standard layout/theme of Latex but I don't
 understand why links need to looks so horrible. A red or cyan square
 around the text.





 Isn't this be configurable?


 Yes, it is. It's just the default for the hyperref package.

 Here is what I use for my D template tutorial (here adapted for the spec)

 \usepackage[pdftex]{hyperref}

 \hypersetup{
      pdftitle={D Programming Language Specification},
      pdfauthor={D Team},
      pdfsubject={D Spec},
      pdfkeywords={D} {programming} {specification} {language} {grammar},
      colorlinks=true,
      linkcolor=red,
      urlcolor=darkblue
 }

 \begin{document}
 ...


I copied that, thanks. The problem I'm having is I can't generate 
internal references properly. They look hot but clicking doesn't do 
anything. Took the usual precautions of compiling several times, no avail.

I'm using \href for the anchors and \label for the targets. What are you 
using?


Thanks,

Andrei
Jan 25 2013
parent reply FG <home fgda.pl> writes:
On 2013-01-25 18:26, Andrei Alexandrescu wrote:

 I'm using \href for the anchors and \label for the targets. What are you using?


\href{url}{text} is for URLs, \hyperref[labelname]{text} is for labels.
Jan 25 2013
parent Philippe Sigaud <philippe.sigaud gmail.com> writes:
On Fri, Jan 25, 2013 at 7:31 PM, FG <home fgda.pl> wrote:

 On 2013-01-25 18:26, Andrei Alexandrescu wrote:

 I'm using \href for the anchors and \label for the targets. What are you
 using?



 \href{url}{text} is for URLs, \hyperref[labelname]{text} is for labels.


I use \href for URLs and \ref or \autoref for internal refs, these
being marked with \label{labelname}.

IIRC, \ref gives a section number, while \autoref gives the 'kind'
("Section 3.2", as opposed to "3.2").
Jan 25 2013
prev sibling next sibling parent Paulo Pinto <pjmlp progtools.org> writes:
Am 24.01.2013 07:26, schrieb Andrei Alexandrescu:

 There's quite a bit of work left to do, but the PDF spec already has 386
 pages of goodness and starts to look seriously cool. Take a peek!

 http://dlang.org/dlangspec.pdf

 (still subject to http://d.puremagic.com/issues/show_bug.cgi?id=9369, so
 don't mind the absent underscores here and there)


 Andrei


Great!
Jan 24 2013
prev sibling next sibling parent reply "Wyatt" <wyatt.epp gmail.com> writes:
On Thursday, 24 January 2013 at 06:26:13 UTC, Andrei Alexandrescu 
wrote:

 There's quite a bit of work left to do, but the PDF spec 
 already has 386 pages of goodness and starts to look seriously 
 cool. Take a peek!


This may just be me, but those margins seem just a _little_ bit 
excessive.  Can we maybe add something like
\usepackage[margin=3cm]{geometry} % ...or 2 or 3.5 or whatever 
looks good
to the top matter? (Though I suppose I can also see the argument 
for keeping it at around 75-80cpl for readability.)
Jan 24 2013
parent Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 1/24/13 12:22 PM, Wyatt wrote:

 On Thursday, 24 January 2013 at 06:26:13 UTC, Andrei Alexandrescu wrote:

 There's quite a bit of work left to do, but the PDF spec already has
 386 pages of goodness and starts to look seriously cool. Take a peek!


 This may just be me, but those margins seem just a _little_ bit
 excessive. Can we maybe add something like
 \usepackage[margin=3cm]{geometry} % ...or 2 or 3.5 or whatever looks good
 to the top matter? (Though I suppose I can also see the argument for
 keeping it at around 75-80cpl for readability.)


Yah, the default LaTeX document class is very generous with margins. 
I'll adjust them in a future pass.

Andrei
Jan 24 2013
prev sibling next sibling parent "Nicolas Sicard" <dransic gmail.com> writes:
On Thursday, 24 January 2013 at 06:26:13 UTC, Andrei Alexandrescu 
wrote:

 There's quite a bit of work left to do, but the PDF spec 
 already has 386 pages of goodness and starts to look seriously 
 cool. Take a peek!

 http://dlang.org/dlangspec.pdf

 (still subject to 
 http://d.puremagic.com/issues/show_bug.cgi?id=9369, so don't 
 mind the absent underscores here and there)


 Andrei


Great. This is just a cosmetic idea, but you could make the spec 
look like TDPL a bit with:

\usepackage[scaled]{beramono}
\usepackage{fourier}

(should be available on all main TeX distributions)

Nicolas
Jan 25 2013
prev sibling next sibling parent reply "SomeDude" <lovelydear mailmetrash.com> writes:
On Thursday, 24 January 2013 at 06:26:13 UTC, Andrei Alexandrescu 
wrote:

 There's quite a bit of work left to do, but the PDF spec 
 already has 386 pages of goodness and starts to look seriously 
 cool. Take a peek!

 http://dlang.org/dlangspec.pdf

 (still subject to 
 http://d.puremagic.com/issues/show_bug.cgi?id=9369, so don't 
 mind the absent underscores here and there)


 Andrei



I believe there are some LaTeX errors around pp. 181 ("alias 
this", "scope class", \textbf here and there), up to 197, pp. 235 
& beyond, p.318, pp.328 & beyond.

Overall a nice work.
Jan 27 2013
parent Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 1/27/13 9:50 AM, SomeDude wrote:

 On Thursday, 24 January 2013 at 06:26:13 UTC, Andrei Alexandrescu wrote:

 There's quite a bit of work left to do, but the PDF spec already has
 386 pages of goodness and starts to look seriously cool. Take a peek!

 http://dlang.org/dlangspec.pdf

 (still subject to http://d.puremagic.com/issues/show_bug.cgi?id=9369,
 so don't mind the absent underscores here and there)


 Andrei



 I believe there are some LaTeX errors around pp. 181 ("alias this",
 "scope class", \textbf here and there), up to 197, pp. 235 & beyond,
 p.318, pp.328 & beyond.

 Overall a nice work.


Thanks, will look into that.

Andrei
Jan 27 2013
prev sibling parent reply Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 1/24/13 1:26 AM, Andrei Alexandrescu wrote:

 There's quite a bit of work left to do, but the PDF spec already has 386
 pages of goodness and starts to look seriously cool. Take a peek!

 http://dlang.org/dlangspec.pdf

 (still subject to http://d.puremagic.com/issues/show_bug.cgi?id=9369, so
 don't mind the absent underscores here and there)


 Andrei


Made one more big pass through everything and now as far as I can tell 
the generated PDF has no major errors:

http://dlang.org/dlangspec.pdf

Take a look!


Andrei
Feb 02 2013
next sibling parent reply Jacob Carlborg <doob me.com> writes:
On 2013-02-02 17:22, Andrei Alexandrescu wrote:


 Made one more big pass through everything and now as far as I can tell
 the generated PDF has no major errors:


The links in the Table of Contents still doesn't work. I'm using Preview 
on Mac OS X.

-- 
/Jacob Carlborg
Feb 02 2013
parent reply Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 2/2/13 11:54 AM, Jacob Carlborg wrote:

 On 2013-02-02 17:22, Andrei Alexandrescu wrote:


 Made one more big pass through everything and now as far as I can tell
 the generated PDF has no major errors:


 The links in the Table of Contents still doesn't work. I'm using Preview
 on Mac OS X.


Thanks. Links remain an unresolved problem for now.

Andrei
Feb 02 2013
next sibling parent reply FG <home fgda.pl> writes:
On 2013-02-02 17:57, Andrei Alexandrescu wrote:

 Links remain an unresolved problem for now.


Might as well leave the internal links black for now.
Overall great improvement!
A much smaller number of page overflows than before.

Only thing bothering me are table captions left on the
previous page, while table body is on the next page.
Perhaps add more stretchable glue before captions?
Feb 02 2013
parent reply Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:
On 2/2/13 12:21 PM, FG wrote:

 On 2013-02-02 17:57, Andrei Alexandrescu wrote:

 Links remain an unresolved problem for now.


 Might as well leave the internal links black for now.
 Overall great improvement!
 A much smaller number of page overflows than before.

 Only thing bothering me are table captions left on the
 previous page, while table body is on the next page.
 Perhaps add more stretchable glue before captions?


Yah, not sure how I can fix that.

Anyhow this thing with non-float tables and captions above them is a bit 
odd. I'm thinking of simply making all large tables longtable, and all 
short table floats. Then the caption would be part of the LaTeX table 
caption, which automatically solves the problem.

If anyone wants to take a look at the TeX source, I uploaded it to 
http://erdani.com/d/dlangspec.tex. I'm stuck in particular on internal 
references.


Andrei
Feb 02 2013
parent Marco Nembrini <marco.nembrini.co gmail.com> writes:
On 03.02.2013 07:24, Andrei Alexandrescu wrote:


 If anyone wants to take a look at the TeX source, I uploaded it to
 http://erdani.com/d/dlangspec.tex. I'm stuck in particular on internal
 references.


 Andrei


I had a quick look, I think you are using the wrong commands. There's a 
nice summary of hyperref commands here:


If I had more time I'd fix it myself :(

-- 

Marco Nembrini
Feb 05 2013
prev sibling parent reply Jacob Carlborg <doob me.com> writes:
On 2013-02-02 17:57, Andrei Alexandrescu wrote:


 Thanks. Links remain an unresolved problem for now.


Compiling this using TextMate gives a lot of warnings about undefined 
hyper references, example:

LaTeX Warning: Hyper reference `pointers' on page 133 undefined on input 
line 7715.

I have used \nameref and \label successfully. Here's a diff where one 
item in the Table of Contents is replaced with nameref:

--- dlangspec_orig.tex	2013-02-03 12:52:01.000000000 +0100
+++ dlangspec.tex	2013-02-03 12:53:37.000000000 +0100
   -108,7 +108,7   
  \setlength{\parskip}{0pt}
  \setlength{\parsep}{0pt}
  \item \hyperlink{intro}{Introduction}
-	\item \hyperlink{lex}{Lexical}
+	\item \nameref{chap:lexical}
  	\item \hyperlink{module}{Modules}
  	\item \hyperlink{declaration}{Declarations}
  	\item \hyperlink{type}{Types}
   -154,6 +154,7   

  \clearpage
  \chapter{Lexical}
+\label{chap:lexical}
    	The lexical analysis is independent of the syntax parsing and the
  	semantic analysis. The lexical analyzer splits the source text up into
  	tokens. The lexical grammar describes what those tokens are. The

-- 
/Jacob Carlborg
Feb 03 2013
parent Jacob Carlborg <doob me.com> writes:
On 2013-02-03 13:09, Jacob Carlborg wrote:

 On 2013-02-02 17:57, Andrei Alexandrescu wrote:


 Thanks. Links remain an unresolved problem for now.


 Compiling this using TextMate gives a lot of warnings about undefined
 hyper references, example:

 LaTeX Warning: Hyper reference `pointers' on page 133 undefined on input
 line 7715.

 I have used \nameref and \label successfully. Here's a diff where one
 item in the Table of Contents is replaced with nameref:

 --- dlangspec_orig.tex    2013-02-03 12:52:01.000000000 +0100
 +++ dlangspec.tex    2013-02-03 12:53:37.000000000 +0100
    -108,7 +108,7   
   \setlength{\parskip}{0pt}
   \setlength{\parsep}{0pt}
   \item \hyperlink{intro}{Introduction}
 -    \item \hyperlink{lex}{Lexical}
 +    \item \nameref{chap:lexical}
       \item \hyperlink{module}{Modules}
       \item \hyperlink{declaration}{Declarations}
       \item \hyperlink{type}{Types}
    -154,6 +154,7   

   \clearpage
   \chapter{Lexical}
 +\label{chap:lexical}
         The lexical analysis is independent of the syntax parsing and the
       semantic analysis. The lexical analyzer splits the source text up
 into
       tokens. The lexical grammar describes what those tokens are. The


Also, remember that you need to recompile it a couple of times to get 
correct references.

-- 
/Jacob Carlborg
Feb 03 2013
prev sibling next sibling parent "TommiT" <tommitissari hotmail.com> writes:
On Saturday, 2 February 2013 at 16:22:41 UTC, Andrei Alexandrescu 
wrote:

 Made one more big pass through everything and now as far as I 
 can tell the generated PDF has no major errors:

 http://dlang.org/dlangspec.pdf

 Take a look!


 Andrei


On page 11 the character '~' isn't displayed on the sentence:

"Adjacent strings are concatenated with the ~ operator, or by 
simple juxtaposition"
Feb 02 2013
prev sibling parent reply Dejan Lekic <dejan.lekic gmail.com> writes:
Andrei Alexandrescu wrote:


 On 1/24/13 1:26 AM, Andrei Alexandrescu wrote:

 There's quite a bit of work left to do, but the PDF spec already has 386
 pages of goodness and starts to look seriously cool. Take a peek!

 http://dlang.org/dlangspec.pdf

 (still subject to http://d.puremagic.com/issues/show_bug.cgi?id=9369, so
 don't mind the absent underscores here and there)


 Andrei


 
 Made one more big pass through everything and now as far as I can tell
 the generated PDF has no major errors:
 
 http://dlang.org/dlangspec.pdf
 
 Take a look!
 
 
 Andrei


Very good, Andrei!

Although I think a more formal (and more boring) specification of the D 
language, a-la C++ specification, would also be welcome. Especially among 
language designers and people interested in compilers and interpreters and 
similar topics.

Kind regards

-- 
Dejan Lekic
dejan.lekic (a) gmail.com
http://dejan.lekic.org
Feb 03 2013
parent reply Walter Bright <newshound2 digitalmars.com> writes:
On 2/3/2013 11:47 AM, Dejan Lekic wrote:

 Although I think a more formal (and more boring) specification of the D
 language, a-la C++ specification, would also be welcome. Especially among
 language designers and people interested in compilers and interpreters and
 similar topics.


Pull requests on the doc are welcome!
Feb 03 2013
parent reply Dejan Lekic <dejan.lekic gmail.com> writes:
Walter Bright wrote:


 On 2/3/2013 11:47 AM, Dejan Lekic wrote:

 Although I think a more formal (and more boring) specification of the D
 language, a-la C++ specification, would also be welcome. Especially among
 language designers and people interested in compilers and interpreters and
 similar topics.


 
 Pull requests on the doc are welcome!


I would gladly help with that if we sit down, and outline the structure of that 
document. DPL team should do this, and we, the minions, should help with the 
rest. :)

-- 
Dejan Lekic
dejan.lekic (a) gmail.com
http://dejan.lekic.org
Feb 04 2013
parent Walter Bright <newshound2 digitalmars.com> writes:
On 2/4/2013 11:21 AM, Dejan Lekic wrote:

 I would gladly help with that if we sit down, and outline the structure of that
 document. DPL team should do this, and we, the minions, should help with the
 rest. :)


All you have to do to get on the "DPL team" is get involved. These groups are 
self-selected!
Feb 04 2013