Skip to content

Correct information about implicit precedence. #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 10, 2012

Conversation

dcsobral
Copy link
Contributor

No description provided.

jsuereth added a commit that referenced this pull request Jan 10, 2012
Correct information about implicit precedence.
@jsuereth jsuereth merged commit c4d8e3e into scala:gh-pages Jan 10, 2012
@heathermiller
Copy link
Member

Great Daniel, thanks a lot.

@jsuereth
Copy link
Contributor

Sorry, merged this before you got to it. Had to feel like I'm contributing somehow :)

Also, Daniel, we may want to add links to the Spec where it discusses name/binding resolution and duplicates the lookup order.

@heathermiller
Copy link
Member

Haha, no problem :)
I was just thinking about said link, only issue is that since we'd be linking to a PDF, how do we point to a specific section? Unless you mean just plain link to entire PDF, then sure.

@heathermiller
Copy link
Member

Either way, just linked to the PDF.

@jsuereth
Copy link
Contributor

We can just link to the section number and the PDF. Hopefully we can
convert that thing to Markdown or ReST or something where we can use
it here directly and still generate a PDF.

On Tue, Jan 10, 2012 at 9:15 AM, Heather Miller
reply@reply.github.com
wrote:

Haha, no problem :)
I was just thinking about said link, only issue is that since we'd be linking to a PDF, how do we point to a specific section? Unless you mean just plain link to entire PDF, then sure.


Reply to this email directly or view it on GitHub:
#31 (comment)

@heathermiller
Copy link
Member

Yep- I've intended to do this for a while.
And I even figured out more or less how to do it. It's just the chunk of time that it'll take to convert it and format it and my own limited availability due to research tasks and teaching that take precedence. I've even tried to pass it off to one or two people interested in helping with small documentation tasks- it turned out to be too long-term of a task for anyone to take it on.

@dcsobral
Copy link
Contributor Author

On Tue, Jan 10, 2012 at 12:15, Heather Miller
reply@reply.github.com
wrote:

Haha, no problem :)
I was just thinking about said link, only issue is that since we'd be linking to a PDF, how do we point to a specific section? Unless you mean just plain link to entire PDF, then sure.

You did see that someone came up with a mostly automated way to
convert the spec into HTML, didn't you? We should get that into the
site, and link to that instead.

IIRC, most of the job was done by Calibre.

Daniel C. Sobral

I travel to the future all the time.

@jsuereth
Copy link
Contributor

Hmm... In 3 months I may have time to take on tasks like this again.
Right now, I'm a bit too full, so I need to finish off a bunch. I'll
revisit with you then to see if I can help.

@heathermiller
Copy link
Member

You did see that someone came up with a mostly automated way to
convert the spec into HTML, didn't you? We should get that into the
site, and link to that instead.

I saw the plain text version- even somehow converting that to HTML automatically doesn't necessarily mean that the result would be user-friendly. When it came time to convert several existing documents from latex to markdown, I spent a good deal of time playing with automated tools which would do the job 60-70% to satisfaction, but ended up converting many things by hand because I had to do less work than correcting issues with the tool. A lot of the headaches have to do with latex macros.

Regardless, I think what we're interested in is one source that can generate both HTML and PDF from. So far, I managed to find a way to do that from markdown or rst, the only thing left to do is convert the latex spec into markdown and I've got to tweak the formatting of the outputted PDF.

@dcsobral
Copy link
Contributor Author

On Tue, Jan 10, 2012 at 12:51, Heather Miller
reply@reply.github.com
wrote:

You did see that someone came up with a mostly automated way to
convert the spec into HTML, didn't you? We should get that into the
site, and link to that instead.

I saw the plain text version- even somehow converting that to HTML automatically doesn't necessarily mean that the result would be user-friendly. When it came time to convert several existing documents from latex to markdown, I spent a good deal of time playing with automated tools which would do the job 60-70% to satisfaction, but ended up converting many things by hand because I had to do less work correcting issues with the tool. A lot of the headaches have to do with latex macros.

You may have missed then that the plain text version was being
generated from the HTML version, the latter being what the PDF was
being converted into. Though, I suppose, you can go directly to plain
text with Calibre. One of the previous suggestions went to HTML first,
though.

Daniel C. Sobral

I travel to the future all the time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants