I am trying to get biblatex print out full author name at first mentioning. I found tex.stackexchange.com/a/46469/36836. But it fails to compile for me. Does it work for anyone here, or do you know another solution?
@Daniel There have been some significant changes to biblatex in the last few months, and neither biblatex-dw nor the answer were updated. Better ask a new question linking to the older one.
@DavidCarlisle If you do the patch level, make sure you use a local install of l3build: I've got to do a CTAN update for the fix re. typesetting documentation/getting hyperlinks right
@DavidCarlisle We could list out all of the files to include in the build.lua scripts: that way you only get exactly what you ask for, at the cost you have to do all of the work by hand (the globs are really just there for the common case)
@DavidCarlisle I always do texlua build.lua clean and svn status (and tidy up) before building for CTAN, so I don't notice this
@JosephWright yes I see that, what I did by hand (and what i might do in a shell script wrapping l3build as doing it cross platform might be tricky) is do svn update; svn status; then complain if there are any M denoting local modified files and remove any ? files that are not under svn control, then do what build ctan does
@DavidCarlisle I'm not a fan of the script deleting anything 'here' except when explicitly asked
@DavidCarlisle It's perhaps worth it for the team stuff: for the common case of one .dtx and one .ins you can easily notice a stray file, but that's harder with the longer file listings
@JosephWright yes in general that's true but make clean asks explictly that in common makefile idioms that and I'm used to make all doing make clean :-)
@JosephWright I almost always have stray files in base as if I edit a dtx file I do tex unpack.ins to check the docstrip guards and pdflatex on the dtx file as a check the doc, (quicker than running l3build on everything-)
proc.cls generated by proc.ins exists
nfssfont.tex generated by nfssfont.ins exists
article.cls generated by classes.ins exists
report.cls generated by classes.ins exists
book.cls generated by classes.ins exists
ltluatex.tex generated by format.ins exists
utf8-test.tex generated by inputenc.ins exists
utf8test.tex generated by inputenc.ins exists
docstrip.tex generated by docstrip.ins exists
ltxdoc.cls generated by docstrip.ins exists
slides.cls generated by slides.ins exists
letter.cls generated by letter.ins exists
@JosephWright surprised about the permissions one I thought I'd fixed those in svn but anyway
@DavidCarlisle OK, I might list out only those files with extensions where we can also end up with them being generated (there's not much point for example listing all of the .dtx files)
Is there a resource that shows/teaches how the (La)TeX macroprocessing works? I am cargo-culting most of what I do with LaTeX. I think I need to learn a bit about the basics.
@wilx the latex format source latex.ltx has examples of most tex macro idioms that get used, the documented version, source2e.pdf has documentation but the quality of the documentation is "variable" (@Joseph might be less polite about it:-)
@DavidCarlisle I'll check the rest of 2e later on: for L3 as I always do the upload it's less risky (particularly as I now do my day-to-day in the Git version so only use the SVN one for releases)
@DavidCarlisle Git offers git clean --f which is handy :-)
@PauloCereda it didn't rain at all in Souldern for the Queens Birthday (that's the good thing about being a monarch, you get two birthdays and can pick the official one to be in the summer when as you show you get good weather)
@PauloCereda that just finds files that are executable locally not ones that svn would make executable if it had a chance
@JosephWright yes but svn has to set the unix style permissions somehow, not sure what windows svn does, cygwin itself is usually fairly sensible so long as you use cygwin tools but if you use any native windows applications on the file then permissions are set by some complicated heuristics that aren't really humanly understandable.
I have come accross seeveeze.com website, which is entitled to help you write your resume without prior LaTeX knowledge.
When you access and scroll down the main page, you will see a very simple CV template, but I did not find out which template is it ? Could it be Moderncv ?
Image :
@HenriMenke You know how confused i am, and license is one part of it. Look at the MDT-template. If you would like, you could say the template guy (no, not me) was stealing the template ...
@HenriMenke But since the CV-site just gives a pdf back, i think this applies
Or more generally: Imagine you are writing a book and sell it for ten dollars. Do David and Joseph get a dime for every sold book? A template is just a layout (this time probably, who knows).
I've found practice with LaTeX makes you faster. Now, I've got a writing disability, so writing out a good copy that other people can read takes me a long time, but I find with practice LaTeX isn't that slow. Also, the first assignment in it, getting the preamble set up and whatnot is the slowest...
@Canageek If you want to write less, you can define a macro \pa{..} that takes everything up to { and gives diferent sizes based on the number, \pa0{..}, \pa4{..}, etc.
Couldn't it be developed an \expanded{..} that would do \edef expandably in LuaTeX. I mean, just one \directlua that expands its argument and then leaves the expanded string in there.
@egreg stop moaning, anyway after today you should get a shiny new latex and can use your crazy charclasses mackage code to have 2000 charclass allocations and forget all about luatex brokenness
@DavidCarlisle It is quite shocking to discover that LuaTeX 0.95 fixes the error that showed up with LuaTeX 0.80 (apart from introducing the bug with KoMa-Script).
I have come accross seeveeze.com website, which is entitled to help you write your resume without prior LaTeX knowledge.
When you access and scroll down the main page, you will see a very simple CV template, but I did not find out which template is it ? Could it be Moderncv ?
Image :
