@daleif if you set openin_any=p lualatex doesn't work at all (it will not input article.cls for example) it only inputs files from the current directory. pdflatex not quite as bad input works but \pdffilesize does not which breaks the new expandable tests for if file exists
@daleif well yes that's all it is (p for paranoid in this case) but it is supposed to be (don't input dot files and files given by absolute path) not (as interpreted by luatex) don't input dot files or any files not under the current directory.
@daleif well I do understand them. It is sometimes difficult to find the relevant files, if there lots of log,out,aux,toc, etc lurking around. But if I wanted a clean folder, I would use the l3build setup: copy everything in a temporary folder and then switch to the folder and compile there.
@DavidCarlisle I had a collegue where I found 2500+ files in a single folder. Most was versions of chapters etc of this book project. He hadn't thought about using version control for his project. Long time ago I had another collegue who named all his files zzz and then the folder told you what this was.
@UlrikeFischer I don't think it is that bad unless you have many latex projects (each with its own full latex doc) in the same folder. Why not a folder pr project.
@daleif well I have seen documents which created five or six index, and acronyms, and glossaries, and so on. That creates quite a number of auxiliary files.
@DavidCarlisle Hello, I've just translated lesson-06 and noticed that there is no explanation about the optional argument (the `[1]` part of the `\kw` definition). The text also says "it is usually best to have just one argument, or sometimes none at all" but without the explanation, a reader can't grasp how they can achieve to define a command which takes no argument. I thought this is a bit strange. https://www.learnlatex.org/en/lesson-06#defining-commands
@UlrikeFischer I agree also that having the intermediate processing files in a subdirectory will be cleaner. I find myself running latexmk -c more often than not. Maybe we could teach latexmk to move then in and out a subdir... hmmm... or prefixing all of them with a dot in front after compilation and remove the dots before...
@wtsnjp hmm, let me read that again (although won't be able to do much before the evening) Actually as I drafted that bit it may be better if someone else comments @JosephWright @UlrikeFischer it is hard to proof read your own code
how do you do new lines in \node? As in \begin{tikzpicture} \node<1->[anchor=west, overlay] at (0, 2.7) {\tcbox{hello\ how are you?}}; \end{tikzpicture}
@DavidCarlisle well one could add in the definition [1] denotes the number of arguments (here one) and #1 denotes the first argument, but as \newcommand\kw[0] actually works, I don't think that one need to discuss the case (and start a discussion about missing spaces ...).
@UlrikeFischer @wtsnjp would Ulrike's suggestion look better to you? just adding in the definition [1] denotes the number of arguments (here one) and #1 denotes the first argument
@Rmano ltx2any does the compilation in a tmp or subfolder and then brings back the pdf to your main folder. Everything stays nice and clean and avoids all the problems of build folders
@samcarter_is_at_topanswers.xyz I didn't try it yet --- but a question, is the tmp folder "stable"? Re-doing the compilation every time would be quite time-consuming. I normally have latexmk running in continuos mode so I have live preview each time I save...
@DavidCarlisle I'm 'slowly' working on that. I've just completed lesson-01 to lesson-06 (and no more-XX has been done). I have noticed additional notes are needed a bit more than I expected, even in the main contents, for the Japanese version. This is because we are using a different engine from the first place (e.g., I have to explain that just using babel is not really enough for Japanese documents).
But for now, I just postpone thinking much about such things and rather just translating as it is in the English version.
@Rmano I think with tmp it tries to reuse if all the files are still there, but I'm not sure (you can also specify the folder yourself to be on the safe side)
@wtsnjp yes we don't currently have any non latin script translations, there are Japanese, Chinese and Marathi translations "in progress" but I would not be surprised if they all have some "issues" to get good text/example balance in practice. Hopefully it works out OK in the end...
@wtsnjp for the babel I don't know. Perhaps you can say "if you are writing a document in a European Language, do this [translation of current example description, but with the existing German text], else [some new text specific to Japanese, or a forward reference to the language-xx lessons or...]
@DavidCarlisle Well, we (I consulted with a few Japanese TeX users including Hisanobu) decided to primarily focusing on Japanese documents with pLaTeX in the main lessons. Thus, English texts (and with other Europian languages) are treated as secondary. This makes the situation further complicated...
You might think we should treat English texts in the main course, but our thought is that is meaningless. Since Japanese people who want to create English documents are already good at reading English, they don't really need Japanese translation. We assume that the expected readers of the Japanese version are people who want to write Japanese documents with LaTeX.
So yes, "getting good text/example balance in practice" is exactly the thing we are aiming for.
@wtsnjp I agree that for most of it you should switch to Japanese being the main focus but I wonder if for just the babel lesson that means you can not say much sensible and there you should keep the existing German text, just as in the English version the text is German (supplied by @UlrikeFischer so it might even be correct German:-)
@DavidCarlisle Thanks. For now, I am almost working alone, but I am planning to ask other Japanese speakers to check the translation because I can't proofread perefectly my own code ;-)
@wtsnjp :-) but at least you don't have the problem of getting the letters "the" in the right order. @UlrikeFischer claims I have sometimes written "teh"
@DavidCarlisle someone has to ;-). But this inch + hoffset business is really a pain. Everywhere people are adding and removing it, and at the end you no longer know where you are ...
@samcarter_is_at_topanswers.xyz that was my PC at work, I had two weeks of vacation, was sick for a week, am back for a week now and had much stress the week before the vacation, so at least a month, I'd say.
@UlrikeFischer On zref again, looking at \zref@labelbylist vs \zref@labelbyprops, it feels to me like they are N- and n-type variants for a comma-list argument: make sense?
@ComFreek the normal log file has the message to run biber (or bibtex) so \input unlikley to be the issue but without any example, hard to know:-) (I never use latexmk personally) if I want biber to run, I type biber seems simpler to me:-)
@JosephWright Yes I'd actually started to write something about arxiv being more prominent in some subjects than others, but I got busy and didn't send it
Is there a quick and simple way to not show any numbers in the bibliography list when using a plain \begin{thebibliography} (i.e. no bibtex or anything advanced)?
I understand that this may sound pointless (the whole point of thebibliography is to add those numbers) but I'm working with an existing document and I only need to switch this off temproarily. I hope not to have to rewrite the thing.
In French and some other European langages, given names should be abreviated keeping digraphs and trigraphs.
John should be abreviated as J.
Clare should be abreviated as Cl.
Charles should be abreviated as Ch.
Christine should be abreviated as Chr.
Philippe should be abreviated as Ph.
etc.
...
@samcarter_is_at_topanswers.xyz regarding ltx2any, I've found this repository: github.com/reitzig/ltx2any/tree/master, last update was in 2018 (same for dev branch)
This is unexpectedly cumbersome. A quick fix was to use backend=bibtex (i.e. not biber) with biblatex. Didn't notice bad effects on my simple reference list, but I'm sure there are some in more complex cases ...
@Ulrike Thanks! It wouldn't be much work to do that for the few affected references, but it would break compatibility with graphical .bib editors such as JabRef (I assume; didn't try, but here it says it's not compatible: github.com/JabRef/jabref/issues/4558 )
@PauloCereda a ltx2any rule for arara would solve the problem :)
(I'm wondering a bit where the sudden wave of "I don't like auxiliary files" comes from. There have been multiple questions about this on stack overflow during the last week)
@samcarter_is_at_topanswers.xyz nobody ever says "I don't want my cross references to resolve"
@JosephWright usage is definitely picking up, you tug video perhaps?
Tue Sep 29 20:51:02 UTC 2020
Number of distinct users: 14
Number of document requests: 314
... Number from learnlatex: 311
Number of documents returned: 219
Number of unique user agents: 11
Mon Sep 28 23:58:28 UTC 2020
Number of distinct users: 7
Number of document requests: 171
... Number from learnlatex: 171
Number of documents returned: 148
Number of unique user agents: 7
Sun Sep 27 23:55:58 UTC 2020
Number of distinct users: 10
Number of document requests: 90
@ComFreek the tex world world is far more change averse than hardware. The vast majority of the code in tex the program and the latex format comes from the 1980s and early 90s.
@ComFreek "not even the GitHub issues are being responded to" This seems to be very unfair! The most recent issue is by the author himself logging a possible new feature June. If we look for open bug reports, the most recent one is from 2018 and need further details from the user who reported. So updates to the program seems pretty much to keep peace with reported bugs.
In French and some other European langages, given names should be abreviated keeping digraphs and trigraphs.
John should be abreviated as J.
Clare should be abreviated as Cl.
Charles should be abreviated as Ch.
Christine should be abreviated as Chr.
Philippe should be abreviated as Ph.
etc.
...
You can use the extended input method:
\documentclass{article}
\begin{filecontents}[overwrite]{ch-init.bib}
@article{key,
author={given=Charles, given-i={Ch}, family=Doe},
title={Some Article Title},
journal={Some Journal},
volume={1},
year={2020}
}
\end{filecontents}
\usepackage[backe...
