The R documentation is a bit of a low water mark. Truly terrible usage of examples.
@PauloCereda I don't follow.
Check out the rsync man page. It may be wordy, but that's how you write example usage.
At the top of pg 7, there is an example showing how to use \IfBooleanTF with a star agument called. The example macro is \foo. But invocation is not shown.
Suggestion: add something telling the users to add a star at the end of the command name. Don't assume they know how to do that just because LaTeX 2e does it like that.
Is there a suitable place to make bug reports for this kind of thing?
@FaheemMitha It's a question of target group. The introduction aims to show what is possible and incrementally advances from simple to more complex subjects. In a documentation it's often the "how", hence it will sometimes aim at developers or at least mention implementation details too. For LaTeX packages the documentation tries to do both.
@FaheemMitha "This basic"? Oh I would call the LaTeX kernel very basic, but source2e is long without real usage examples and to be honest I wouldn't really want it to contain some, because then it would lose its value for quick research.
@FaheemMitha Well it wouldn't hurt to show a \foo* in the documentation, but on the other side everyone who has read an latex introduction should have seen all the commands like \chapter*, align* etc with a star. So the hurdle to understand it is rather low.
@UlrikeFischer I've been using LaTeX since 1996. Now, I freely admit I may be brain-damaged, but I suspect here are many other similarly brain-damaged users around.
And one should be kind to the brain-damaged users. One day, you might be among their ranks.
Not you, personally. I meant that as a general comment.
@JosephWright Thank you for the pointer. I'll add a quick note, before I forget all about it.
@FaheemMitha to be honest while this is running over latex2e as opposed to a stand alone format with self contained documentation, i would expect that basic knowledge of latex syntax: * forms [] for optional arguments and {} for mandatory arguments can be assumed in the xparse manual. It is not intended as a beginners tutorial for latex2e.
@FaheemMitha It can always happen that you suddenly don't understand something because you miss or forgot some really simple point or because a documentation doesn't mention something everyone else thinks if obvious. The xparse documentation doesn't mention a lot of other obvious things, e.g. that commands can have arguments, that command names should consist of letters etc ...
@JosephWright I am the maintainer of that website. You may notice it has not been updated in a long, long time. I suppose you will get a notion of the current state of affairs here: ncm.gu.se/normat
@PauloCereda -- lots and lots. mostly from organizations that have an international presence, but also a great big explanatory one from the ams executive director telling us all what we should do when we get a request from someone in the eu.
@JosephWright -- you probably don't really want to add it, but since mathjax uses latex math syntax, it might be worth mentioning that it has a different purpose and is not equivalent to or even related to latex.
@JosephWright -- if you're going that route, mentioning that even microsoft allows some (la)tex syntax for math under certain circumstances. but i wouldn't guarantee that it produces the same results.
@barbarabeeton At present, mainly cleaning up existing answers: here, I wanted to get rid of the ANT one (it's vanished from the internet), but keep some historical data. A question on alternatives seemed reasonable.
@JosephWright I look at some emacs screenshots... and I even tried once, but I couldn't find anything "better" then what TexStudio offers me. Actually it was the opposite.
@DavidCarlisle You can use the 'edit' link to see that it's not in the main dir
@DavidCarlisle Of course, one could argue that flat is fine ... I just think longer-term some automated division would be easier. Of course, dividing everything up would be a lot of work.
@DavidCarlisle I guess what I really mean is I'm not sure whether it's truly useful: I don't think one can set up the index list from the file structure, rather from the tag/category YAML ...
@DavidCarlisle Can do: might be a good plan anyway (I'm trying to get us to a stable structure 'a bit at a time')
@JosephWright perhaps leave the file move for a bit, having the toc auto generated would be good as it would make it easier for people to contribute new questions if you just need to add one file with a metadata at the top that makes it get slotted in
In relation to my previous question in this link Change part with arabic number, I would to obtain, using the Legrand orange book source and his structure.tex file, an appendix (in italian language) done only with the letters of the alphabet.
So for example:
The several parts, different from...
@egreg I have been changing my question for three hours but with my long code I can not get what I want. Thank you. I'm going to sleep that tomorrow I'm at school. Hello
In relation to my previous question in this link Change part with arabic number, I would to obtain, using the Legrand orange book source and his structure.tex file, an appendix (in italian language) done only with the letters of the alphabet.
So for example:
The several parts, different from...
