@barbarabeeton I had lecture notes written with amslatex (that used LaTeX 2.09+nfss); then LaTeX2e came out with amsmath and @ was no longer active, so my arrows had to be retyped with \xrightarrow. It used to be in amslatex that was essentially a straight port of amstex.
@DavidCarlisle Yeah, exactly-, but why do you call it raised? Is it not a \newline, \par, or the like. Does it have to do with the open/close group at the end? I don't believe I have any, or that any are inserted- the command on my end is like this `. . . #8 \color{...}\\}
@vlg finally you start to show some code..,, I assume (I have to assume as you have given no hints) that there is no \par or \newline but that as I showed you have a bad group or space. The {..} you show in that fragment looks suspicious for example as \color does not take a text argument (but you may mean the ... is the color name such as red, hard to tell). It must be trivial for you to make an example, just take the document you have and delete everything except that...
@vlg ... one cell and then delete every package not used in that table cell and end up with a small document just consisting of a one row table.
@CarLaTeX Have you ever think of cleaning answered questions from your favorite list? I see all questions here, for instance, are now answered, and mostly solved, therefore you can unfavorite it!
@JouleV Yes, I clean the list when the answers which don't interest me are answered, but there are also my actual favorites, which I don't want to clean
@MarcelKrüger if you have time to look at the new bug (I don't have it ...) it would be probably best to base it on the branch I made yesterday night, it contains your last fix and the newest fontloader code.
@DavidCarlisle \color{ uses a predefined RGB val, however, it was the extra space between #8 and the color that did it. How wrong I was to ever believe I can leave in an unaccounted for space.
@subhamsoni The center of the arc (i.e. the center of the circle/ellipse the arc is a seqment of) is determined by the start angle and radius you specify. If (X) is your start point, the center is at (X) - (start angle:radius) where (start angle:radius) is in polar coordinates.
is dot below used for anything other than arabic transcriptions, and how many of these are commonly used?
1E04;LATIN CAPITAL LETTER B WITH DOT BELOW
1E05;LATIN SMALL LETTER B WITH DOT BELOW
1E0C;LATIN CAPITAL LETTER D WITH DOT BELOW
1E0D;LATIN SMALL LETTER D WITH DOT BELOW
1E24;LATIN CAPITAL LETTER H WITH DOT BELOW
1E25;LATIN SMALL LETTER H WITH DOT BELOW
1E32;LATIN CAPITAL LETTER K WITH DOT BELOW
1E33;LATIN SMALL LETTER K WITH DOT BELOW
1E36;LATIN CAPITAL LETTER L WITH DOT BELOW
1E37;LATIN SMALL LETTER L WITH DOT BELOW
1E38;LATIN CAPITAL LETTER L WITH DOT BELOW
1E39;LATIN SMALL LETTER L WITH DOT BELOW
@barbarabeeton @JosephWright (anyone:-) I'm wondering if we should predefine them...
@DavidCarlisle -- There are some letters in transcriptions of Sanskrit that have underdots. (Sorry, I'm not fluent in Sanskrit ... but in any case, it isn't Arabic.)
A question about an edit that recently appeared on the tex.meta site. A title and corresponding text in the question Welcome to TeX.SE was changed trivially from TeX.SX to TeX.SE by a relative newbie (with association rep at 101). I've been using the notation "tex.sx" since I joined this site. What is the practice of other old-timers? I've noticed both forms, though I personally still prefer "tex.sx".
@barbarabeeton .se is the normal network abbreviation but there were reasonable objections from Sweden (I an sure there is an existing meta.tex.sx question about that) and the recommendation here was to use sx
The 'official' position across the network is to use 'SE', so that is what I use when talking to people on other sites. However, 'SE' is the TLD for Sweden, and 'SX' (or 'sx') fits nicely with 'TeX'. So on the site I and many others use a variation of 'TeX-sx' (TeX-SX, TeX.SX, etc.).
@UlrikeFischer -- In the U.S., line breaks are assumed to be possible after em-dashes. However, there are situations where em-dashes are used in place of parentheses, and then a line break after the first doesn't make sense. A careful editor (human) would have to make a judgment call in that case. This is something I should look up before pontificating.
@egreg I tried (with the extension in 2015 or so) to cover all the single-accent diacritics that are"easily" covered by T1 encoding and predefined accent constructs, but obviously missed this whole block of dot under
@DavidCarlisle I just had to implement a work around for someone as the used (unicode) font neither had a \d{h} glyph nor the combining accent, but I have no idea how they used it (but I doubt that it was arabic).
@barbarabeeton I have the problem, that the fontloader code of luatex "eats" an hyphen and so gives an en-dash instead of a em-dash dashes---eaten. The suggested fix to set \automatichyphenmode=1 works, but has the side effect to suppress line breaks after the em-dash (but also after the hyphen if it is at the begin of a word). I'm wondering if we will get lots of complains if I change this.
@UlrikeFischer -- Eek! Seems to me there's something wrong there. Does it also eat the first hyphen of an en-dash, giving just a hyphen? I've certainly seen em-dashes at the ends of lines where a line break would be both appropriate and beneficial. I suspect that making the suggested fix would serve to confuse people; I don't like putting forced breaks into source text, and the only alternative I can think of to avoid that is to insert \hspace{0pt} after an unruly em-dash.
@barbarabeeton no it eats only from em-dashes (and only if input as ---, Hans comment about it is, "it's about time that texies start using the proper unicode symbols instead of these funny ligatures". I must say, from a german view \automatichyphenmode=1 is the better default: we don't have em-dashes without spaces, but often words starting with an hyphen.
@UlrikeFischer -- Then it sounds like the \automatichyphenmode=1 is the better approach. Do you know if that would prevent a line break after the hyphen in expressions like $p$-adic? That does sometimes get an unwanted line break unless something is done to prevent it.
@UlrikeFischer still would seem more natural ordered the other way, also mixing break points choice with turning - into a discretionary seems strange, but it's only a name....
My cousin's daughter boyfriend has just converted her thesis from Word to LaTeX. She didn't want to write in LaTeX directly, but now she is enthusiastic of the result: a new LaTeX fan in the world!
If yes, wouldn't be more "correct" if the \[...\] delimiters go to the system environment i.e. \[\begin{system}...\end{system}\] instead of newenvironment?
Thanks!!
I think this new environment should work as align i.e. without \[...\] but I am not sure
@UlrikeFischer quite possibly same reason that gif support was removed from ghostscript (and dvips if I recall correctly) stupid patent rule around that time...
@manooooh looks Ok to me (you might want to put \ignorespacesafterend after the \]
@manooooh ^^ see the cases env is taking up invisible space for the second column that you were not using, so when centred it appears further to the left
@DavidCarlisle I would like to be just as much with you as with @egreg: I liked your proposal better than the one that egreg answered here: tex.stackexchange.com/a/476123/152550 Could you post an answer so I can accept it, please? You have had the idea, I did not even know of the existence of aligned
@manooooh \lvert is essentially the same as \mathopen| and \rvert is \mathclose|. The odd result of \sin|x| and |\sin x| was the origin for them in AMS-TeX and then in amsmath: \sin\lvert x\rvert and \lvert\sin x\rvert have correct spacing.
What is the "best LaTeX practices" for writing absolute value symbols? Are there any packages which provide good methods?
Some options include |x| and \mid x \mid, but I'm not sure which is best...
@egreg yes yes... I just went crazy because sometimes I need the command to inline math and sometimes to display
Because, as you said, it is wrong to always use \left and \right in inline math
But if I only use `\abs` then if I have something like `vmatrix` it is not the same size :( So I have to add `\makeatletter \let\oldabs\abs \def\abs{\@ifstar{\oldabs}{\oldabs*}} % \let\oldnorm\norm \def\norm{\@ifstar{\oldnorm}{\oldnorm*}} \makeatother`
@egreg ok. It still seems to me that there is plenty of space at the end, but you are right: as the parentheses are larger there are more side bearings
@egreg I find it much more advisable to use \abs* since it alerts the user who is reading the code that "Hey, now comes an absolute value". In contrast, with \left|\right| it is not very clear. Why do you say "For small pieces of text, \abs is more convenient, though"?
@manooooh Habits, perhaps. I find $\abs{x}$ better than $\lvert x\rvert$. But if the code in the argument of \abs is large, it becomes difficult to find the closing brace, unless the code is laid out properly as shown above.
@egreg in both Overleaf and TeXnicCenter you can know the pair of symbols by just passing the mouse over any of them, so the problem of not finding an opening or closing symbol no longer exists (at least for me):
Of course if you are programming with plain code you do not have this features, but meh
The 'official' position across the network is to use 'SE', so that is what I use when talking to people on other sites. However, 'SE' is the TLD for Sweden, and 'SX' (or 'sx') fits nicely with 'TeX'. So on the site I and many others use a variation of 'TeX-sx' (TeX-SX, TeX.SX, etc.).
What is the "best LaTeX practices" for writing absolute value symbols? Are there any packages which provide good methods?
Some options include |x| and \mid x \mid, but I'm not sure which is best...
