Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6book, 2010-06-09

| Channels | #perl6book index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
05:12 hirschnase joined #perl6book
05:52 dalek book: 54a4228 | util++ | src/subs-n-sigs.pod:
05:52 dalek book: [subs] Fixed "order-burger" code example
05:52 dalek book: Concatenation op (~) has tighter precedence than Conditional op (??!!)
05:52 dalek book: review: http://github.com/perl6/book/commit/54a422885549cea991f19935836fd6b8af2e780c
06:58 hirschnase joined #perl6book
07:00 hirschnase joined #perl6book
07:43 cognominal joined #perl6book
08:41 masak joined #perl6book
11:58 hirschnase joined #perl6book
12:17 masak joined #perl6book
17:45 dalek book: bbf179b | pmichaud++ | README:
17:45 dalek book: Update README with additional Ubuntu 10.04 package names.
17:45 dalek book: review: http://github.com/perl6/book/commit/bbf179b609890939ad22954cf798a66e31390c01
17:57 dalek book: 96911a0 | moritz++ | src/basics.pod:
17:57 dalek book: [basics] typo noticed by patrickas
17:57 dalek book: review: http://github.com/perl6/book/commit/96911a074954d8e7c7849527ada5e7bd8f357396
18:09 Wolfman2000 joined #perl6book
19:04 uvtc joined #perl6book
19:07 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
19:10 uvtc moritz_: Not sure I understand. Is it tedious to write code examples in LaTeX?
19:10 moritz_ uvtc: yes
19:11 uvtc Ah. AUCTeX makes that easier.
19:11 moritz_ uvtc: verbatim environments are OK, but inline code sucks
19:11 moritz_ \verb|1+2| vs. C<1+2>
19:11 moritz_ what's AUCTeX?
19:13 uvtc Thanks for the example. AUCTeX is the Emacs module that provides some key combos that make typing the LaTeX commands faster/easier.
19:14 uvtc 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:15 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 moritz_ s/1/a/
19:19 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:20 moritz_ being an often used format doesn't make it more suitable here
19:21 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:22 uvtc (those style quotes, I mean)
19:23 moritz_ shouldn't be hard with translated pseudopod either
19:24 moritz_ in both cases it's a matter of actually doing stuff
19:25 moritz_ my problem is that I don't know how to create floating side nods in LaTeX that don't interfere with verbatim environments
19:26 moritz_ once I know how to do it, it's easy to emit the appropriate code
19:27 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:28 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.
19:28 moritz_ because those are not kinda like flushleft
19:28 moritz_ s/not//
19:28 moritz_ and latex only deals well with actual blocks, or so
19:29 uvtc (re. floats & verbatim) Ah. I haven't looked at that aspect.
19:30 uvtc (sorry, guess I didn't read your earlier reply carefully enough)
19:31 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 moritz_ for scientific content, I've found latex to be more direct
19:31 moritz_ for programming stuff, I've found POD to be more direct
19:31 moritz_ YMMV
19:32 uvtc Ok, well, I thought I'd throw it out there. Thanks.
19:32 moritz_ that's appreciated
19:32 uvtc :)
19:33 masak joined #perl6book
19:36 uvtc left #perl6book
22:29 dalek book: 2df1ea2 | util++ | src/subs-n-sigs.pod:
22:29 dalek book: [subs] Added section on Currying
22:29 dalek book: review: http://github.com/perl6/book/commit/2df1ea2b91a5236397f8ec557f4b8774194c10a5
22:29 dalek book: fc9b935 | util++ |  (2 files):
22:29 dalek book: Merge branch 'master' of github.com:perl6/book
22:29 dalek book: review: http://github.com/perl6/book/commit/fc9b935939ed410c2b9d67ee12d55906c991b545

| Channels | #perl6book index | Today | | Search | Google Search | Plain-Text | summary