Why is it that makeindex cannot normalize index commands such that two spaces is the same as one space. Come on, lines breaks in \index commands are common.

Is there an option to normalize?

I normally use texindy, which normalizes, but makexindex does not seem to do so.

Ahh, the -c option.

@daleif I get one index entry from \index{hello world} and \index{hello world}. What are you doing exactly?

@UlrikeFischer This exact problem:

foo bär

@DavidCarlisle How can one not love complex numbers with tex.stackexchange.com/a/716176/82917... ?

Note that the first foo bar has two spaces between, the latter only one.

@campa @DavidCarlisle giving a quick answer, to get closer to his beloved Italian.

With makeindex -c the foo bar's are collaped as one. Why is this not the default. Especially when most latex editors just lists the makeindex command as makeindex %.idx or similar.

@daleif hm, doesn't happen if I use the index package instead of makeidx. (you lost the second space in your example but I got the point).

@UlrikeFischer I tend to forget to use the single spaceformatter when pasing in chat. Also the index package is from 1995?!

or at least the texdoc on it is

-c saved the day. I hadn't noticed.

@UlrikeFischer @daleif or use \foo{\index{....}} with \def\foo#1{#1} index reads its argument verbatim, probably it really shouldn't.

@daleif the latex companion writes that spaces are harmfull and -c should be the default ...

@UlrikeFischer PartII, page 351 last line of the page.

@barbarabeeton ooh twitter.com/shouldhaveanima/status/1782237264455905405

@samcarter ooh twitter.com/dhelglore/status/1782193251145155035

@barbarabeeton the soundtrack makes it even better twitter.com/AMAZlNGNATURE/status/1782086665210659004

@PauloCereda ohh!

@UlrikeFischer, the test for the entry being cited you mention in tex.stackexchange.com/a/716110/87678, is that in my code or the standard biblatex code? It's been a while since I spent enough time on this style!

@DavidPurton that is in biblatex itself, I got the same behaviour also without the sbl style.

@UlrikeFischer Ta. I admit, it seems like it should work

But at least it's not directly my fault :)

@DavidPurton ooh

@Skillmon OK, this works and seems to be faster with a add of \ExplSyntaxOff

@Skillmon Here "undifined controll sequence". Whaterver my old \cardcolor-command is not that wild.

@cis the \cardcolor macro above needs a \makeatletter ...\makeatother around it.

@Skillmon Ah, I understand.

@PauloCereda -- Both are good, but the one with the music is absolutely delightful! The swans, after all, were using the crosswalk.

@barbarabeeton gentleswan :)

~2sec. per page.

@cis Maybe Stich-probe can go on one line?

@mickep Mmmhh... critical.... What if "1500. Stichprobe"...

@mickep clearly solution is to use a language with shorter words

@cis Well, do as you please, I would make it fit for all numbers.

@DavidCarlisle Indeed, like Finnish.

@cis I don't understand that, but never mind.

@DavidCarlisle I don't understand that either.

@mickep Well, the numbers that pgfmath calculates are perhaps correct to 1-2 places after the decimal point.

@mickep translate.google.com/…

@DavidCarlisle Aha! Too tired...

(I saw sample, specimen, sample book when marking it, but did not get it...)

@DavidCarlisle 抽样 is probably better (= drawn sample)

但是，当然要看情况——

@JasperHabicht but... surely you are not arguing with the oracle of perfect translations?

@DavidCarlisle =) there exists no perfect translation

only approximations

@JasperHabicht everyone has to have faith in something. I have faith in google translate:-)

@DavidCarlisle It is a nice tool that converts "Dose" <de> to "peut" <fr> (via "can" <en>) ... so, I have only very limited faith in it =P

@DavidCarlisle Those tools were very useful in Chiina. :)

Are there plans to try to bring accessibility to mathematical expressions in LaTeX or is that better suited to MathML?

@LaTeXereXeTaL see the examples here github.com/latex3/tagging-project/discussions/72

@Cattleya \immediate\write is not \iow_now:Nx. \iow_now:Nx is \exp_args:NNx \iow_now:Nn . I.e., it does x-expansion and then sets \newlinechar to the number of the code point of the lineefeed character and then does \immediate\write with preventing expansion via \unexpanded and then resets \newlinechar to its former value.

So you cannot have single explicit character tokens of category 6(parameter) in \iow_now:Nx's 2nd argument unless in a way where they get detokenized in the course of x-expansion. You can have pairs of explicit character tokens of category 6(parameter) whereof the first one gets removed and the second one gets doubled. \iow_now:Nx is definitely not the same as \immediate\write.

You could have looked up via \cs_show:N. The expl3-pendant of \immediate\write is \tex_immediate:D \tex_write:D.

@Cattleya On my pdLafTeX \cs_show:N due to character translation prints the carriage return character in ^^-notation as ^^M. However \newlinechar by default denotes the linefeed-character, and therefore \cs_show does a linebreak for the linefeed-character.

If \newlinechar was set to -1, then with my pdfLaTeX you would get a linebreak as well as unlike the carriage return character the linefeed character is not translated to ^^-notation and therefore is delivered to the shell as is and the shell does a linebreak when displaying it.

@Cattleya I use TeX Live 2023 and the TeX Live guide says that character translation is configured in cp227.tcx. And when looking into cp227.tcx, you can see that the linefeed-character (LF) is made printable. But there is no directive in that file for making carriage return printable.