@daleif People do that but the official position is you are meant to define your style yourself. There's of course a question of how much flexibility one can build into an interface and how you deal with small changes in big pieces of code
@JosephWright But can you have enough callback points (or what ever) to meet all user requirements of inserting this and that in strange places due to weird requirements
After updating packages this morning nothing works anymore (I am working under Windows 8). Particularly, compiling files with TeXWorks returns the message:
running 'initexmf --quiet --update-fndb' to refresh the file name database
The operation failed for some reason.
This is of little help, un...
@daleif I added a comment. Imho it is due to the missing "autoinstall new things" feature in miktex and so you can run into troubles if you update binaries and then check for new package first. There is a new miktex-log4XX-package and there has been a report that things breaks if you don't install them first. I'm away now and will be back in around two hours ...
@JosephWright what exactly are the convention of using : in data macros. If I use \cs_set_nopar:cn {test-test}{data} it keeps bugging me that there should be a : in the name. (Perhaps I'm using the wrong macro?) But in other contexts, such a format is not imposed: \seq_get_right:NN \l_yo_a_seq \l_prefix
@daleif Variable names do not contain :, which is used for the argument spec. of a function (macro). There is of course the question of whether an argument-free macro is a function (\my_foo:) or a variable (\l_my_foo_tl). I tend to think the latter is best used for something containing mainly 'text' whereas the former is more for 'actions'.
Say I want to make the following (etoolbox syntax) \newcommand\setData[2]{\csdef{data-#1}{#2}} in expl3, I was trying \cs_set_nopar:cn{data-#1}{#2} internally, but get the missing : error.
@daleif To me this looks like a token list, so I'd do \tl_set:cn { data- #1 } {#2}, but if #2 is more about 'actions' then \cs_set:cpn { data- #1 } {#2}
@daleif Yes
@daleif @FrankMittelbach and I strongly favour the :Npn version, but others on the team like the convenience of the :Nn version so it is a permanent feature of expl3
@daleif Functions with no arguments are more for 'programming' contexts, e.g.\cs_new:Npn \my_foo: { \my_foo_auxi: \tl_if_empty:NTF \l_my_tl { \my_foo_auxii: } { \my_foo_auxiii: } }
@barbarabeeton @egreg following this post on meta: meta.tex.stackexchange.com/questions/6267/… , I'm thinking to write something about how to create a class template step by step for TUGboat. I never create any class before, so it will be from a total beginner point of view. Interesting topic or not?
@yo' The question was about 'data store' like cases, so they are not really functions. Moreover, my reading of the question was that the data storage names are perhaps meant to work outside of expl3 (perhaps as a user argument)
@JosephWright yeah, well, I more meant, if you dynamically create cs's, you still should follow the L3 naming scheme I suppose. And then provide a public "caller", if need be ... ?
@JosephWright at least with a user interface. For example my playing around with fancyref, I need to store what say the prefix thm corresponds to (perhaps even language dependent, but that is another matter). And was looking at what the proper method for storing information like this would be in expl3. I guess I'd better start looking at the siunitxsrc
Module luatexbase Error: Attempt to use callback.register() directly. on input l
ine 146
! LuaTeX error /home/davidc/texmf/tex/latex/base/ltluatex.lua:112: See luatexbas
e Error
stack traceback:
[C]: in function 'error'
/home/davidc/texmf/tex/latex/base/ltluatex.lua:112: in function 'module_error'
/home/davidc/texmf/tex/latex/base/ltluatex.lua:119: in function 'luatexbase_err
or'
/home/davidc/texmf/tex/latex/base/ltluatex.lua:295: in function 'register'
./xinputenc.lua:50: in function 'register_callbacks'
@JosephWright ^^ shouldn't we put the message in the error() so it comes on the ! line not before (also we ought to have a line break not . as followed by on input line
@daleif If you look at siunitx, go for the v3 sources (in development) as the v2 (release) code has been co-developed with the 'rules' and doesn't always follow them! github.com/josephwright/siunitx/tree/master
@JosephWright I've fixed up the messages not to end with . need to check implications of just using error() partly as I'm not sure I understand this, what's the difference between these, why do we need to write each line separately?
for _,i in ipairs(msg_format(mod, "Info", text):explode("\n")) do
texio_write_nl("log", i)
end
texio_write_nl("log",msg_format(mod, "Info", text))
@JosephWright it matters in the error case as you want the whole message before (or at least not after) the error which is why it's currently making the message before the error line. But if we can do the whole message in one go then can easily use error not texio_write_nl . Will experiment a bit later....
@yo' Bullets in the margin (which has nothing to do with hanging punctuation) are used by Bringhurst. The example with bullets inside the type block cannot be deemed “incorrect” (but I'd prefer a small indentation of the bullets): it's just stylistical preference. The example with the “pull quotes” is hilarious: the closing quote in the right margin is simply stupid.
@yo' There's a timing problem: the value of \labelsep will be set to the normal interword space relative to the font that's current when the setting is performed.
@egreg yep, that's what I meant. But I of course set up fonts first, so it should be fine in most cases (hopefully the space is not much different in the italic font, well, I can test this.)
anyway, it looks too tight to me, I should probably aim at the inter-sentence space
! LuaTeX error ./ltluatex.lua:106:
Module luatexbase Error: Attempt to use callback.register() directly
(luatexbase) on input line 146
stack traceback:
[C]: in function 'error'
./ltluatex.lua:106: in function 'module_error'
./ltluatex.lua:115: in function 'luatexbase_error'
./ltluatex.lua:291: in function 'register'
./xinputenc.lua:50: in function 'register_callbacks'
[\directlua]:1: in main chunk.
l.146 \directlua{xinputenc.register_callbacks()}
% font definitions, try \usepackage{ae} instead of the following % three lines if you don't like this look \usepackage{mathptmx} \usepackage[scaled=.90]{helvet} \usepackage{courier}
@Gigili Because the information about the position of the equation elements are written to an auxiliary file on the first run, and used on the second run.
@PauloCereda Would there be a straightforward way of pairing an output directory with a jobname? So could I do something like %arara: pdflatex: { jobname: [foo, bar], output-directory: [dir1, dir2] } and have dir1 be the output directory for foo and dir2be the output-directory for bar?
@PauloCereda Again, no need to worry about this all that much, if it proves to be a pain. I have a working solution at the moment. :)
@AdamLiter I couldn't include this in the default engine rule because I don't feel it is something the majority of users would need. But it is surely possible, I can even write this rule for you. :)
Is there a way for me to fetch some mail from the LuaTeX list? I registered myself now, but I would like to reply the previous messages.
@RomainPicot -- i do find that an interesting topic, but there's a more urgent question to be answered first: exactly what is a template? to my understanding, a document class is not a template, and vice versa. a template (to me) is a basic outline, providing basic required commands (like \documentclass) and recommendations (usually as comments) for desirable or often-used (but not universal) features. however, that "definition" isn't universally agreed. (cont'd)
@barbarabeeton Interesting. What I consider a template can contain a specific document class. For instance, what I presented at TUG15 (including the minimal document code) is a template for me.
@PauloCereda Fair enough, that makes sense. :) I haven't installed 4.0 yet and don't know how rules are written, so if you're not opposed to doing that for me, that'd be nice, but I can always figure it out on my own at some point, too. :)
@Sverre It is `twoside. If you have the book (or article) laying open in front of you, and some times the left page is a bit shorter, sometimes a bit longer it looks horrible.
@ninja please read the advice the site gives on how to construct a question, the one posted there isn't really answerable. You should be able to construct an example without requiring external link
@Sverre it's because \subsection{Sjølvstendet til folkemålet} is moved to the next page, plus \flushbottom because of twoside. Had you been using memoir, you could have issued \raggedbottomsection to stop this stretching when a \section is moved to the next page.
This also explain why the top bibliography entry on my last page remained dashed - it's because it's on an odd page, so the reader will see the author's name on the even page ... this is the first time I've compiled a two-side document :)
@Johannes_B Right! I actually just added them because I suspected my redefinitions of the line spacing had something to do with it. I'll remove them again. Thanks :)
@daleif Deleted ... the problem was that the document had to be compiled exactly the way it looks now for the issue to appear, so I had to keep the fonts in the zip :-/
@barbarabeeton I see two different things that could be named template now. 1 - The way to organized a preamble and 2 - the document layout produced by (La)TeX compilation. What I was thinking is the 2nd one. So: "How to create your own class" if I rewrite what I mean
@JosephWright not done anything really other than replace callback.register, so now I'll be able to have tests without luatexbase (via fontspec) complaining I'd been bad....
@Johannes_B hmm, might be better for the auctex mailing list. Actually getting \citeto work properly in my Emacs (regexp searching the bib file), does not always work for me either. Might be a version issue.
@Johannes_B If you use master .bib in your texmf tree you can do this, not sure if that's what is needed: `(setq reftex-plug-into-AUCTeX t) (setq reftex-default-bibliography '("~/texmf/bibtex/bib/master.bib")) (setq reftex-bibliography-commands '("addbibresource"))`
@PauloCereda I'm sorry to tell you I've been learning emacs... but you might be heartened that I'm also learning scheme and XML
@PauloCereda I am moving from dissertation to book and I thought TEI-XML would give me more flexibility when dealing with publishers who want Word documents and can't deal with TeX. But it's still a new experiment for me.
The history about the pica pint is quite interesting (at least for me). And it has to do with the way we measure types.
In the beginning
From the early days of the emergence of the printing press, and the mythical Gutenberg and for a long time, each printer, each workshop had its own way of mea...
@1010011010 -- tex's "pt" is the traditional printer's point. there are 72.27 of them to an inch. this measurement predates computers by at least a century, and computer printers by even more. (adobe really wasn't doing anyone a favor when it redefined the point to be exactly 72 per inch; that "point" is called a "bp" = "big point" in tex.)
After updating packages this morning nothing works anymore (I am working under Windows 8). Particularly, compiling files with TeXWorks returns the message:
running 'initexmf --quiet --update-fndb' to refresh the file name database
The operation failed for some reason.
This is of little help, un...
