@PauloCereda The hwyaden has mistaken preferences. I can't be in the lead. I never was in the lead, and it wouldn't count now anyway. I shouldn't have been there at all.
@egreg We still have some open questions about directly using pdfLaTeX files with the Unicode engines: the font encoding is one area, but input encodings and inputenc is another (@DavidCarlisle is worrying about that one)
@JosephWright testing adding \@currname into the includeinrelease tests, assuming that's Ok, will check it in in a bit, then need to look again re-implementing it all again:-)
@s__C topsep=-anything looks wrong although without a test example hard to say exactly what will go wrong
@s__C setting topsep negative makes the space above and below the list smaller, and potentially negative, isn't that what you intended? That could perhaps be described as "somehow ignore" the paragraph spacing, depending what you mean, but without an example, hard to say:-)
\begin{document} This is a list: \begin{itemize} \item Bla \item Bli \begin{itemize} \item Oh \end{itemize} \item Blo \end{itemize} %With some blabla after. % problem if this line is commented
And between two paragraphs? Here it's not working.
well the space after a list (that doesn't start a paragraph) is topsep +parskip and you made that total 0 so you get no space. If that isn't what you intended, what was the intention of setting topsep to -\parskip ?
@Johannes_B -- they're not exactly the same; although enumitem is suggested in the older one, the actual recommendation (and it's a nice one) is to use titlesecsince it's sections that are being numbered. i guess maybe just ignore the similarity. thanks.
@barbarabeeton Oh, i didn't notice that the older is on sections. I was wondering why titlesec plopped up there. Leave the old one alone and just retag the recent?
@Johannes_B -- i've already done some retagging, so maybe the new one's okay. (though i'm sure i've seen it before.) i've now also found some other questions about section numbers in the margin, so maybe a different approach, with cross-reference(s) on the older one.
@barbarabeeton I found a bunch of questions/answers yesterday that all proposed a low level KOMA command that should only be used if absolutely necessary. I hope people will find the solutions on site that give the right command.
@s__C unlike the underlying latex list params where it uses the same space before and after the list enumitem has separate keys to control space before and after (I think it was @Johannes_B who gave an answer using that to a question recently)
Load the package enumitem and add the following lines to your preamble
\setlist[enumerate]{after={\bigskip}}
\setlist[itemize]{after={\bigskip}}
MWE
\documentclass{article}
\usepackage{enumitem}
\setlist[enumerate]{after={\bigskip}}
\setlist[itemize]{after={\bigskip}}
\begin{document}
\begi...
@DavidCarlisle but in my case it wouldn't work. I want a \parskip when the list ends before the next paragraph. bu if the list is part of a paragraph that is continuing, then no \parskip after the end of the list
@s__C well normally (without enumitem) latex uses \topsep if there is no paragrah break before the list and \partopsep if there is (a paragraph break after the list is always ignired
I am new to LaTeX. I am writing an article in LaTeX but at the moment I am not sure what should be the final layout of my article; so, I am writing it in IEEEtran format. I thought that it would be easy to change the layout later if required.
But I read a book on LaTeX and I found the following ...
@JosephWright -- there's a specific example in the question about an ieee class, and there are a couple of comments on that point that could be turned into a cogent answer about how to shift between document classes without too much pain. maybe changing the question itself to "how can i change the layout of an article if the class i'm using isn't suitable?"
@Johannes_B @JosephWright @barbarabeeton It's true that it could be re-worded to "how to switch from article to ieeetran. However, I have a feeling that this would be really just mechanical copying of passages of ieeetran manual...
@yo' @barbarabeeton I think this is the classical »search for template« thing. Using article and a few of the thousands CTAN packages would be my guess of an answer.
@yo' -- actually, i was thinking of it from the perspective of "how to switch from ieeetran to article. the suggestions for that are in the comments, but i doubt in the ieeetran manual.
@PauloCereda so far. But Adobe declared to stop releasing the linux versions, so in some time, when people start to use the new versions' features, we're screwed
Holy cow, I just broadcasted my iMac screen to my Apple TV and all of a sudden I had everything in the TV. That means I can watch @egreg and @DavidCarlisle battling for rep points in my living room! :)
@Johannes_B To be honest, I was thinking of something along these lines: an app with lots of photos of ingredients in which she just had to select which ones apply to a particular recipe and the type some info on how to handle them. Then the app would generate the .tex file based on the selected input and we would have the recipe. :)
@Johannes_B my minister's wife says: the iPad is great: you look into your fridge and pantry, put the 3 least useful things there in google, and a recipe pops up using exactly these three things. So you put the the iPad on the empty shelf you have in your kitchen and start :)
To the downvoter: If you have to downvote a newcomer's question, then at least have the dignity to comment on what do you think is wrong with it. — yo'23 secs ago
Another question: is there any way to avoid the 'unused global options' warning for a custom class. (I'm using l3keys2e and run \ProcessKeysOptions and then \ProcessOptionsX...
@DavidCarlisle page 158/159 of interface3.pdf includes it in the recommended template for \DeclareDocumentCommand, so I've been repeating it but I'm not sure why.
@DavidCarlisle No. It is complaining about an option which is used. And it definitely recognises this in some sense because the option works.
\DeclareDocumentCommand \MyModuleMacro { o m } { \group_begin: \keys_set:nn { mymodule } { #1 } % Main code for \MyModuleMacro \group_end: }
I just wondered why when I wasn't using it with 'ordinary' syntax. (i.e. I translate a macro into expl3 and suddenly I need a group.)
@DavidCarlisle Possibly. Probably not though. Probably I've failed to do something I'm meant to to keep it happy. Much more likely than a bug. Oh, well. I have plenty of other warnings, what's one or two more?!
@cfr it depends on the use, but for example I use groups in includegraphics (which uses keyval of course not l3keys but it's same thing. If you go \includegraphics[width=2in]{zzz} you probably don't expect the value of the width key to be set to 2n when you come to the next \includegraphics
@DavidCarlisle Oh, OK. So I could leave it out if I wanted to create a macro which needed to set a key which would have an effect outside that context? Sorry, this is probably a dumb question, but it all still rather alien.
@cfr yes keys are really just \def in disguise so if you have a command like \hypersetup{zz=zz} then obviously you want the key setting not to be scoped as it is documented as affecting the document, but normally keys are used more like \includegraphics where the expectation is that any settings are local to that one command
@saadtaame For instance, with \begin{scope}[fill=blue] you can make all draw commands inside be blue-filled. If you later decide to change it to red, you gotta do only one change, not mmany
@Joseph another typo in interface3: part I, section 1, paragraph "c", double "So So". As well, I noticed that the interlineskip is missing between first paragraph of a macro description and the next one, throughout the whole document. This can be seen for instance in I.2, between the two paragraphs of \ExplSyntaxOn
@yo' Well, I find it hard to imagine given the specific nature of what you're attached to, but I get the general idea. [Don't you get fed up just waiting for Adobe things to open?]
@yo' It is a PITA on mine :(. It takes forever to start, and then it has this long indolent phase where it just kind of sulks and refuses to talk to anybody before eventually, grudgingly agreeing to spew complaints at me. (Initially, I used to think it was frozen and kill it but, actually, it just takes a long, long, long time to thaw.) May not help that it is 32 bit, of course.
Document Class: ctu1 2014-01-18 v0.1 CTU ONE
)
! Missing = inserted for \ifnum.
<to be read again>
-
l.2 ^^M
?
I tried twice, each time writing the file from scratch
file ctu1.cls:
\RequirePackage{expl3}
\ProvidesExplClass{ctu1}{2014-01-18}{0.1}{ CTU ONE }
ok, found it. @Joseph Please, could l3bootstrap manual show the expected date format? the error message above almost drove me away from l3 crazy. Thanks :)
I fortunately know for a while that the right thing is interface3, and I actually have alias i3 = interface3 in my texdoc.cnf
@cfr that's something I want to avoid. My previous class (available online, I can share the link if you want) is a 30kB tex+2e monster. This one's gonna be pure l3
@yo' The thing is, if I didn't mix them, I'd never use expl3 because the idea of starting would be too intimidating! If I can think, 'I'm just going to figure out how to do this macro...' then it is within the realms of possibility.
@cfr and I think the other way around. I've got a new project to start, and I think I can manage to make a reasonably nice l3 code with the first try. We take a long time on the design anyways, so I have some time to master that on the way :)
The Welsh ordinals are systematically wrong in every LaTeX bit of code I've seen, and every bit of non-LaTeX code I've seen. babel, polyglossia, datetime...
@egreg But it shouldn't complain anyway. It is not the main document language and I don't define or use any glossary terms in any non-English context. I just need a very little Greek and a bit of Welsh.
@egreg And the one I get about glossaries-greek? She must be insane if she's sending ME messages, subliminal or otherwise, suggesting I make glossaries-greek!
@cfr You can tell me from this what arguments \correspondingauthor takes? :D
\def\author@bracket[#1]#2#3{
% increase number of authors by one
\advance\X@author@cnt1
% save author's short name and full name
\expandafter\def\csname X@author@no@\romannumeral\X@author@cnt\endcsname{{#1}{#2}}%
% add commas in case this is not the first author and add author into all three lists
\ifx\@cleanauthor\@empty\else
\g@addto@macro{\@cleanauthor}{, }%
\fi
\g@addto@macro{\@shortauthor}{#1}%
\ifx\@shortauthor\@empty\else
\g@addto@macro{\@shortauthor}{, }%
\fi
@yo' I did not mean to claim more than I claimed. I meant what I said. I did not mean a whole bunch of other things I did not say! \newcommand etc. have severe limitations in terms of what you can do. But they are not (to me) any less clear than the xparse equivalents.
@JosephWright I did not mean to claim more than I claimed. I meant what I said. I did not mean a whole bunch of other things I did not say! \newcommand etc. have severe limitations in terms of what you can do. But they are not (to me) any less clear than the xparse equivalents.
@cfr Second point is that \newcommand doesn't use \protected, which really should be used for document commands unless they need to be expandable (rare, and still perhaps an area needing refinement in xparse)
@cfr Oh, by the way, try \newcommand\foo[2][]{\showtokens{#1}}\foo[[bar]]{baz} and compare \DeclareDocumentCommand\foo{om}{\showtokens{#1}}\foo[[bar]]{baz}
@cfr Or try a runaway argument part way through the chain (these last two features were tricky)
@yo' I actually think they serve a useful purpose which the xparse versions do not: they provide a relatively simple interface for people who want to implement something relatively simple. If all that had been available was the xparse stuff or the \def stuff, I never, ever would have tried to do anything. Having learnt to use those made a difference. [xparse wasn't probably written when I learnt \newcommand but that's not the point.]
@yo' Yes, but it took me a long, long time to figure that out - even though I had used \newcommand etc. for quite a while, and delved some way into \def and friends.
This always makes me think of these sets of cards they use to test children's language development. There is/was a shortage of Welsh speakers qualified to do this. Also, the set of cards was just a translation from the English. And that's where the problems started: not knowing 'duck' in English does not indicate the same developmental stage as not knowing 'hwyaden' in Welsh!
@yo' You must have linguistically sophisticated ducks if they can manage accents like that.
@cfr by default feminine (kachna). but there is a masculine-living word for the male (kačer) and a neutral word for the young (kachně or archaic káče). Then a word for a little one (no matter the sex nor whether it's adult) is feminine kachnička
A while ago I was talking to David in this room and he said to make a class I should use \LoadClass{article}\def\zzz{zzzz}- what does the backslash after def mean?