« first day (309 days earlier)      last day (4611 days later) » 

5:14 AM
@JosephWright The list of all Stackexchange sites, at Stackexchange.com has that info (though not as accurate).
 
 
4 hours later…
Hello @Raphink :-)
 
what's up?
 
nothing much, I just woke up. =P
you?
 
fine
 
9:34 AM
work
 
I like that art wallpaper. I'm gonna add it to my desktop. =)
 
the guy has several
what's nice is that he explains which fonts he uses
 
very cool!
Nice, the memoir vs. koma bounty went to lockstep!
 
yes
that was a hard decision to take :-)
 
It was a great idea to start bounties on some questions.
 
9:44 AM
well the two others didn't get answers yet :S
 
10:03 AM
I need a release name suggestion.
The previous one was Tasty Waffles.
 
for what?
what does the product do?
 
for an app. =)
it's the tex.sx thread printer.
 
thread printer?
 
yep, this one. =)
I'm about to release v1.1.
I wrote Apple Pie, but it's not that good. =P
 
ok
interesting
@PauloCereda that reminds me of the book functionality of wikipedia
 
10:09 AM
:-)
 
is your machine really fast or did you speed up the movie?
 
I had to speed up. =P
 
hehe
;)
so you're parsing the HTML and generating tex ?
 
I'm really slow on doing stuff. =)
Yeah, that's the idea.
I try to guess most of the code, but sometimes the generated tex has errors.
at least, it's just a matter of correcting the code.
 
yes
so it's a reverse tex4ht
 
10:13 AM
Far from it, it's just a humble app. ;-)
 
ok ;)
most big projects begin as humble apps
and there's humble apps that are much more useful than big bloated apps
give me cator echo a hundred folds over MS Office ;-)
 
so true. :-)
haha
 
 
4 hours later…
2:10 PM
Now, after I moved back to Germany, I was looking for some LaTeX events nearby. I found some but only for the other kind of latex events :-D
3
 
2:33 PM
haha! Case-sensitivity strikes again.
 
@MartinScharrer I think they get advertised on d.c.t.t
 
2:56 PM
We have no TUG in here AFAIK. sigh
 
3:18 PM
@PauloCereda I did not know about this!?
Fits nicely into my question on Meta...
2
Q: Printable version of questions/answers or entire discussion

WernerI don't know how kosher this is for online forums and whether there will be green-erds cringing, but how about adding a feature to be able to print a question/answer or even an entire discussion? Of course, over on Math.SX, LaTeX formatting is interpreted to present mathematics (via MathJax) as g...

@PauloCereda You're calling it a humble app. Should be humble pie then.
 
@Werner Oh, I hope this app can help. =)
 
@PauloCereda The coverage is patchy - we have few people in UK-TUG from abroad, as it's cheaper to join us + TUG than to join TUG directly :-)
 
@PauloCereda Looking at your (regular speed) video it seems to do exactly that. Does the PDF output also include any uploaded images?
Your example (123.pdf) shows a post that didn't include any images, while the other one displaying TeX output (21090.pdf) does.
So, I guess it does.
 
@JosephWright Cool, I didn't know that. I'll see if I can get my international credit card again and join a group.
 
@PauloCereda We (UK-TUG) take wire transfers (or PayPal to me), along with the usual cheques :-)
Taking PayPal as a group is a long-standing aim, but the rest of our committee are not keen. So I have to manage as best I can (I'm Secretary of UK-TUG)
 
3:31 PM
@Werner Yes, it does. =) I also put a replacement image in case the image isn't available anymore. The only difference is that the PDF embeds the images, while the tex output downloads the images.
 
@PauloCereda Nice. That's good.
Without pushing the limits here, does it work for meta as well?
Well, I guess that won't be interesting. So scrap that idea.
 
I don't like the PDF output, as it's very basic. I had some suggestions on calling pdflatex under the hood, but I can't rely on that mostly because (i) I'd need to use a system call, and that would require a TeX install, and (ii) there are cases in which the generated tex has errors (that I can't handle).
 
@PauloCereda Makes sense.
 
@Werner I could add it in the next version, it's very easy since main and meta share the same structure. =)
@Werner I'm not sure of how the app behaves on multiple-page threads (and the ones with lots of comments). Since tex.sx uses a lot of Ajax stuff, it would require multiple calls. But I believe that the app works for the average thread. =)
@JosephWright Hm I'll take a deeper look. It seems interesting.
 
@PauloCereda I just discovered it now, so I'll let you know if there is an above-average thread that causes problems. :)
 
3:39 PM
@Werner That's awesome, thanks a lot!
 
Top-right of the web page texprinter.sourceforge.net I get a broken image link to Github.
 
@Werner Ouch, I should've relied on an internal image. =)
Ribbon is fixed. =)
 
@PauloCereda Looks much cleaner. :)
 
@Werner hehe :)
 
4:01 PM
@Raphink I've added a comment about package emulation in memoir that softens lockstep's point somewhat, although the point is well-taken.
 
thanks @AlanMunn. In any case, the bounty is awarded already
 
@Raphink I understand. I wasn't trying to change your mind. Lockstep's answer is a very good one (and it's your bounty to do with what you want.)
 
@AlanMunn interesting point nonetheless
:)
 
4:19 PM
Flashback:
 
@AlanMunn See my answer.
 
if anyone wishes to vote
and herbert answered both ;-)
 
11
Q: What can't TeX do?

jetxeeWhat are TeX's limitations in typography, book design and publishing? (and here TeX also includes all its derivatives, like pdfTeX, LuaTeX, and macro packages built upon it, LaTeX, ConTeXt etc.). Some things (like math and references) are extremely easy in TeX. There are some things that are har...

"TeX can't bake cakes" - Priceless.
 
it can't make your wife happy (not everyday at least)
but it can make her unhappy (if you spend all your time texing)
 
haha
 
4:37 PM
@lockstep Good to know. That does seem to be a serious limitation in this case. For most other kinds of emulation, this might not be such a problem.
 
@AlanMunn Perhaps @egreg can comment if my understanding of the inner workings of memoir.cls is correct.
 
@lockstep Yes. I would assume that he is aware of the \DisemulatePackage command, so the problem with index generation is actually deeper than just memoir's emulation of the index package itself. His imakeidx package is pretty clear on its being incompatible with memoir.
 
5:39 PM
@AlanMunn Yes, by now imakeidx is incompatible with memoir, but I'm working about it; it seems that it's sufficient to disable memoir's indexing macros and changing it into ours.
 
@egreg @lockstep's answer to KOMA/Memoir question really hits the nail on the head about compartmentalization of functionality. It's very much a double edged sword, though. For example, Vafa Khaligi's bidi or Heiko's hyperref has do be individually tweaked for every package; having a more packages makes that harder not easier. So there are arguments on both sides of the issue for sure.
 
@Werner: I need a translator. The answer is to long for my English ;-)
[Change page margins for one single page inside the document](http://tex.stackexchange.com/questions/27562/change-page-margins-for-one-single-page-inside-the-document)
You can't disable the warnings. This behavior bases on the algorithm of `typearea` / `recalctyparea`. `\recalctypearea` calculates with the last page settings. But by using `landscape` the changing of `textwidth` / `textheight` are more than 15%. (This is the allowed penalty). `typearea` ignore the changing of the page orientation. Maybe in the next relea
 
5:56 PM
@AlanMunn Sorry, but I can't find the earlier message which you are referring to.
 
@Marco You can't disable the warnings. This behaviour is based on the algorithm of typearea / recalctyparea. \recalctypearea performs its calculations with the last page settings. But by using landscape, the changes to \textwidth and \textheight are more than 15%. (This is the allowed penalty). typearea ignores the modification of the page orientation. Maybe in the next release Markus Kohm will add such a feature.
@Marco Seems like the backticks got lost in translation there.
:-/
 
@Werner Thanks
I answered.
 
6:12 PM
@Marco I saw!
 
6:22 PM
22
Q: What are the strengths and weaknesses of Koma-Script and Memoir?

xportTo make a professional book layout, many people suggest to use either Koma-Script or Memoir. Let me know the strengths and weaknesses for each please.

It's this one.
 
6:55 PM
@AlanMunn Thamks, I've added a comment.
 
7:20 PM
\textbf{testing}
worth a shot heh
 
@TylerGillies It's Markdown here :-)
We don't use MathJax or similar (on the main site or here), as we usually want to see the source!
3
 
@JosephWright oh good point
 
Goal!
 
7:36 PM
the cool thing about \LaTeX is that the documentation for the various packages/modules is usually pretty well documented, or at least looks nice aesthetically
 
8:08 PM
@TylerGillies There is one notable exception: look at the documentation for tabu. :(
 
there are more exceptions I'm afraid
I've seen some horribly documented packages
even some horrible code
 
@egreg Or minitoc.
 
@AlanMunn Oh goodness, all of those maps :-)
 
@JosephWright As Caramdir said a while ago "I'm not saying that the manual isn't unnecessarily verbose. Just that only about 3.8% of the manual is actual user documentation."
4
 
8:24 PM
Does anyone have recommendations/comments/feedback on r.pinson.free.fr/calvary/pdf/sagesse_cs.pdf ?
 
@Raphink This font looks so soft and clear to me, does it use any special hinting?
 
@AndreyVihrov what do you mean by hinting?
 
@Raphink Very nice looking book. A couple of comments. The dropcaps (initials) to me look a bit odd jutting out to the left margin. Also, if you compare e.g. Jan 21 and Jan 22 the height of the initial relative to the rest of the line seems to vary quite a bit. (In fact, is this just about 'L'?)
 
http://en.wikipedia.org/wiki/Font_hinting
CM/LM and Times, which I usually see when reading PDFs, look all washed out compared to this.
 
ah
@AndreyVihrov the font is EB Garamond
@AlanMunn thanks
 
8:34 PM
On second look, it's more general than 'L'. Compare e.g. Jan 28 and Jan 29.
 
@Raphink The sectioning headings of the Introduction and the Index differ in their vertical alignment. Did you just switch to \twocolumn? If yes, use my idxlayout package (and hereby avoid LateX bug 3126).
 
@AlanMunn some initials are raised (it's the case of the L, Q and J iirc)
 
@Raphink The Q looks too high and the L too low, IMO. (But I can see with the Q, the long tail might look bad if it's not raised.)
 
@lockstep the index uses: `\usepackage{imakeidx}`
`\makeindex[title=\indextitle,intoc,options=-s bibleref.ist,columns=2]`
 
@Raphink: very nice book!
 
8:42 PM
@AlanMunn: yes. I have to raise the Q so that it doesn't touch the 3rd line. As for the L, it's a really hard one to set up
 
@lockstep a little advertising: idxlayout saved my layout. =)
 
@Raphink Strange -- IIRC, imakeidx is based on multicol, too, and so vertical positioning should be correct. Did you change the margins in any way?
@PauloCereda Well, it's only multicol plus some key--value interface. :-)
 
@lockstep the margins for the whole book are set using \areaset
I'm wondering if Caslon Initials might look better @AlanMunn
 
@Raphink But you do notice there's a difference, don't you?
 
the code is here by the way : github.com/cc-translators/sagesse
@lockstep you mean a bigger margin in the index?
 
8:46 PM
@Raphink No -- a smaller top margin.
 
oh my, this caslon initials font doesn't look nice
ah, the top margin!
that will be my fault for sure :-)
probably some titlesec settings that are different
 
@Raphink I see that. What if you increased the size of the L (only)? (But I'm sure you've played with this a lot.)
 
Is this the way Caslon Initials is supposed to look? Looks like playing an old FPS game
@AlanMunn I'll try
@AlanMunn the L is already 10% oversize
and not raised
 
@Raphink If it is, I agree, this isn't anywhere near as nice as what you have.
 
@Raphink There's more: Compare the headings for February 5th and 6th -- clearly a different vertical positioning. Could this be caused by the accent in "Éternels"?
 
8:49 PM
@Raphink So maybe raise it a bit, and/or oversize it more?
 
@lockstep that is possible :'(
@lockstep I'm inserting \vfill in 6 places in the page to align the first and last lines. It shouldn't affect the title positioning though, should it?
 
@Raphink It could do.
 
There's no \vfill before the title
only after
@AlanMunn I can't raise the L otherwise it won't be aligned with the second line of the text
@lockstep, @AlanMunn what could I do to ensure that titles are properly aligned?
 
@Raphink I think @lockstep is onto something with the É. If you replace that temporarily with just E does the title line up again?
 
@Raphink I think the accents (or whatever they are called correctly) are the culprits. Look at the heading for March 5th.
 
8:55 PM
@Raphink Yes, that's why I thought maybe oversizing it more would be better. (But you have much more experience with this than me.)
 
right
@AlanMunn I've put 15% oversize
now
@lockstep yes, clearly
@lockstep I think somehow the index reacts differently to the same titlesec settings
as for the intro
no idea why
 
Entry for June 10th: I spot an overfull hbox. ;-)
 
hehe
switching to LuaTeX helped a lot
 
June 26th, too.
 
I'm also reducing the amount of words I put in small caps after the initial
which tend to generate overfull boxes
and are not typographically correct
so usually just restricting to one word in sc after the intial fixes this
I just haven't do that in june yet
 
9:01 PM
@Raphink Isn't there a way of specifying the exact height of a box and letting things go outside of it? I'm not sure how this would be incorporated into the titlesec commands, though.
 
@AlanMunn there's titles on one line, others on two lines
so a fix height box wouldn't do
:S
 
@Raphink What about markup for words with accented uppercase that uses \smash or something?
 
@AlanMunn you mean instead of using the unicode encoding?
 
@Raphink No, would it be possible to have a command \foo{} that puts the word into a smaller box, so that the whole line doesn't get messed up?
 
hmm
I'm not sure to understand exactly how
 
9:08 PM
@Raphink Add a strut at the start and end of the title; you probably need to use a customized strut: \vrule width 0pt height x, where "x" is the height of an accented uppercase letter. Or change the baselineskip and topskip for the titles to account for accented uppercase letters, if titles are more than two lines long.
 
what is a strut?
 
@egreg Thanks Enrico. That's exactly what I had in mind, (actually the strut idea is sort of the opposite, since it will drop every line, but the basic idea is exactly the same.)
 
im trying to use tug.dk/FontCatalogue/teenspirit, but it says i don't have emerald package. im using mactex anyone know the easiest way to add font packages from CTAN?
 
@lockstep is the alignment for the index heading better now? r.pinson.free.fr/calvary/pdf/sagesse_cs.pdf
 
@Raphink It's an invisible object which has a height and possibly a depth. There is the \strut command, which inserts such an object that fits exactly the baselineskip (70% height and 30% depth). In your case the baselineskip is probably not suitable for the font. I'll try and do some experiments.
 
9:14 PM
ok
@egreg the code is over at github.com/cc-translators/sagesse
make sagesse_cs.pdf
 
@Raphink Much better. :-) And I like the overall design and layout of your book.
 
@lockstep for the record, this is a translation of an american book. The original version is amazon.com/Wisdom-Today-Chuck-Smith/dp/1597510319
I've copied the layout quite a bit, but changed the fonts mostly
I also don't think the original was made with TeX :-)
even if I had wanted it, Adobe Charlemagne would have never fit with the French text, which is far longer than the English one
@egreg so your idea is to make it so that even if there's no capital with accents, it will take the same vertical space as if there were, so that the letter are aligned, right?
 
Nevermind i figured out how to use system fonts with xelatex
 
@TylerGillies fontspec is your friend.
and with TL2011 now, you might want to give a try to LuaTeX, which is supported by fontspec, can do pretty much the same, and has better microtype support.
 
9:30 PM
The problem is that your "É" is 12.76 points high, while the baselineskip is only 25pt (and 70% is 17.5pt. If you don't need that the possible second lines keep into account this height, then add \titlestrut after \dayheadfont\huge in the definition for titlesec.
\newcommand\titlestrut{\vrule height 12.8pt width0pt\relax}
This will lower the titles a bit, they can be raised at will with \titlespacing.
 
@egreg I'll try that thanks
@egreg I'm not sure I'm getting the 70% part just yet
basically, the \titlestrut command forces the line to get 12.8pt points, right?
whether there is a letter that need such a height or not
@egreg: I get an error: ! Package titlesec Error: Entered in horizontal mode.
after doing : \newcommand{\secstyle}{\filcenter\dayheadfont\huge\titlestrut}
 
@Raphink OK, put it after \filcenter, that's where the title is finally read.
 
let's try that
nope, same error
I put it after the second \filcenter in the before field of \titleformat and it seems to work
let me check in various places
ah, no :'(
 
9:49 PM
@AlanMunn: Today I uploaded a new version of mdframed and I add a version history ;-) Thanks for the inspiration.
 
@Marco You're welcome. Glad I could help. It's a really useful package.
 
`\titleformat{\chapter}[display]
`{\dayheadfont\huge}`
`{}{10pt}`
`{\vspace{-25mm}\filcenter\titlestrut}`
 
that's the chapter titleformat though
and the problematic titles are sections
I'm trying to add \filcenter here github.com/cc-translators/sagesse/blob/master/…
I mean to add after \filcenter there
but that doesn't fix it
 
Someday, I hope to understand what you guys are talking about.
=)
 
@PauloCereda if you look at the 5th and 6th of february (Février) in my PDF for example
you'll see the titles are not aligned
that's because exact spaces are added before the titles, but the É in the title for the 6th is bigger than all othe letters in the title for the 5th
 
9:58 PM
@Raphink the final \filcenter
 
so @egreg is suggesting a way to fix that
 
@Raphink hm I'm gonna take a look.
 
@egreg yes?
@egreg what I'm doing is this:
\titleformat{\section}[display]
{\secstyle} % format
{\seclbl} % label
{-7pt} %sep
{
\ifthenelse{\isodd{\thepage}}%
{\fancytab{\chaphead}{\arabic{chapter}}}%
{}%
\filcenter\titlestrut} %before
but it doesn't change anything
 
@Raphink Shouldn't the strut be in the \sectstyle part?
 
@AlanMunn I tried that, it failed complaining about being in horizontal mode
 
@TylerGillies :-)
@egreg I think I understood the problem.
before is typeset before the whole title, which means before the label, which in my case is the day and month above the main part of the title
so it won't work
I could try to put it after the label
` {\seclbl\titlestrut} % label`
I'll try that
I'll give it a width just to debug
hehe
 
10:21 PM
@Raphink And if you put it before the \filcenter in the "before" code? (Working with a simplified version of your code, that seems to work.)
 
of which filcenter? the last one?
it works
 
@Raphink Yes.
 
but it starts under the baseline
so it's got to be higher than 12.8pt
like 25pt does the trick
@egreg seems we have a solution
@AlanMunn @egreg just reuploaded with the fix
 
10:49 PM
thank you very much guys
 
11:25 PM
Still up @PauloCereda ?
oh yeah, it' snot that late there ;-)
 
@Raphink: I'm back! :-)
I had some pizza while reviewing a paper. =P
Now I'm really curious to try Unity. I guess I'll download Ubuntu and see how it looks.
 
ah
Unity ;-)
I switched to Linux Mint mainly so I don't have to use Unity
 
really?
 
de gustibus et coloribus...
it's nice on a netbook
but on a 24" screen, not really
 
I know what you mean. ;-)
 
11:39 PM
alright, let's call this a day
Good night
 
Good night, buddy!
 

« first day (309 days earlier)      last day (4611 days later) »