irclog.perlgeek.de/perl6book/today | source: github.com/perl6/book/
Set by moderator on 8 June 2010.
05:12 hirschnase joined
dalek ok: 54a4228 | util++ | src/subs-n-sigs.pod:
[subs] Fixed "order-burger" code example
 05:52
06:58 hirschnase joined 07:00 hirschnase joined 07:43 cognominal joined 08:41 masak joined 11:58 hirschnase joined 12:17 masak joined
dalek ok: bbf179b | pmichaud++ | README:
Update README with additional Ubuntu 10.04 package names.
 17:45
ok: 96911a0 | moritz++ | src/basics.pod:
[basics] typo noticed by patrickas
 17:57
18:09 Wolfman2000 joined 19:04 uvtc joined
uvtc Was just reading about this week's challenge/contribution... regarding tweaking the appearance of the pdf, is there any interest in foregoing the POD and instead writing the book in LaTeX? 19:07
moritz_ uvtc: no. I find POD with many code examples *so* much easier to write than plain latex
uvtc moritz_: Not sure I understand. Is it tedious to write code examples in LaTeX? 19:10
moritz_ uvtc: yes
uvtc Ah. AUCTeX makes that easier. 19:11
moritz_ uvtc: verbatim environments are OK, but inline code sucks
\\verb|1+2| vs. C<1+2>
what's AUCTeX?
uvtc Thanks for the example. AUCTeX is the Emacs module that provides some key combos that make typing the LaTeX commands faster/easier. 19:13
I haven't used LaTeX in a year or so, but I think the key combo for inline verbatim probably gives you that "\\verb||" and puts the cursor between the pipes. 19:14
moritz_ well, if I have the choice between a) making a translation by program and b) forcing everybody to use clever editors than I usually chose 1) 19:15
s/1/a/
uvtc I only know Emacs, but my guess is that most powerful editors come with some kind of LaTeX support. And the basics of LaTeX are not too bad (to learn and use). People who tend to write documents tend to be familiar with LaTeX. :) 19:19
moritz_ being an often used format doesn't make it more suitable here 19:20
uvtc I suggest LaTeX because I think it would be easy to get nicely fine-tuned PDF output. Also, because it shouldn't be hard to get «these». 19:21
(those style quotes, I mean) 19:22
moritz_ shouldn't be hard with translated pseudopod either 19:23
in both cases it's a matter of actually doing stuff 19:24
my problem is that I don't know how to create floating side nods in LaTeX that don't interfere with verbatim environments 19:25
once I know how to do it, it's easy to emit the appropriate code 19:26
uvtc Personally, I don't mind if the block floats to the side or is in the middle with the text. They both look fine, IMO. My only opinion here is, LaTeX is built for writing things like books, and so it might make the path to completion smoother. As an aside, it's not too onerous if you primarily stick with its defaults. 19:27
moritz_ the problem is that floats don't interact well with verbatim envs 19:28
uvtc I've also found (though, maybe it's just because of the circles I run/ran in), that many folks have at least passing familiarity with LaTeX, and don't have any major problems with it.
moritz_ because those are not kinda like flushleft
s/not//
and latex only deals well with actual blocks, or so
uvtc (re. floats & verbatim) Ah. I haven't looked at that aspect. 19:29
(sorry, guess I didn't read your earlier reply carefully enough) 19:30
moritz_ my point as an author is that I want a markup format that's direct to write and read. The technical details of translations are usually left to the publisher (though in this case we're helping the publisher) 19:31
for scientific content, I've found latex to be more direct
for programming stuff, I've found POD to be more direct
YMMV
uvtc Ok, well, I thought I'd throw it out there. Thanks. 19:32
moritz_ that's appreciated
uvtc :)
19:33 masak joined 19:36 uvtc left
dalek ok: 2df1ea2 | util++ | src/subs-n-sigs.pod:
[subs] Added section on Currying
 22:29
ok: fc9b935 | util++ | (2 files):
Merge branch 'master' of github.com:perl6/book

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!