@enthu I think it's ultimately about habits. I mean I don't know what a pure programmer is but I would wrap your enumeration the other way around concerning programmers I do know. Programmers are using their keyboard very intensively. Because their hands are at their keyboard all the time it is easier to just type some shell commands then to search for that mouse thingy to click things.
When working with terminals and shells it's also natural to use Linux over Windows because even the new Windows Terminal is far from what Linux shells provide. And you can customize Linux even more to be keyboard-only by using tiling window managers while you have certain problems using Windows only with a keyboard in an efficient way.
Same with word, programmers use their text editor all day so they like plain text manipulation, version control etc.; Word is inferior to TeX in that regard. Ultimately, I think it should not be the logic of liking the hardest, just the logic of working too much in front of a screen to not optimize productivity towards own habits ;)
@samcarter_looks_forward_TUG'21 expl3 has \c_max_int, but I don't think that there is an equivalent in latex2e, it is not something you really now. Imho everything above 100000 should be more than fine in your case.
@TeXnician thank you, I like your point of view. Yes you are right. Working with keyboard is very important for them. For me, I am not a professional programmer who has everything in mind. So I should alwyas use mouse to open browser, search for code to get myself out of the hell and move to the next hell! :)) so in my experience being fully text and shell dependent has never been easy at all. Professional programmers are not the same.
They have everything in mind and the only time consuming thing should be the time they spend to write things.
@samcarter_looks_forward_TUG'21 tyes, it's called \maxdimen
@AlexG I think basically it comes down to using a different top level script than ps2pdf and as noted earlier if we use a different script there are several ways to control the ps commandline.
@samcarter_looks_forward_TUG'21 either that or you would have to contemplate the possibility that I was wrong. Hmmm "7FFFFFFF is perhaps a more natural way of writing it.
@AlexG only half but I didn't try very hard. If a solution requires to change the calling script, then it is imho much easier to add a comment to the PS and to ask Akira to change the ps2pdf script so that it parse the file. The script use lua, so it should be easy to do. The main question is how to encode the version. Is e.g. a comment like %%PreferredPDFversion: 1.7 allowed?
@AlexG well yes, it sometimes complicate things when there are two ghostscripts around, but in this case it would be really useful, if texlive had the control over the scripts.
@UlrikeFischer apart from the non trivial problem of getting users to call a different script having a new script just for texlive would work OK. texps2pdf or whatever
@DavidCarlisle well not every user has to use them, only user who care about the pdf version and don't want to use command line options. Imho a special script would at least help with the testsuites, so I think we should try it. The first step is to agree about a sensible comment and test if we can get it into the ps @AlexG
@UlrikeFischer yes but the users won't know when they need them and won't know how to configure the pipelines in their editor configuration when they do....
@UlrikeFischer @DavidCarlisle There are guidelines for non-Adobe DSC comments. Not sure whether it is mandatory to register them with Adobe: See Section 9 in www-cdf.fnal.gov/offline/PostScript/5001.PDF
@AlexG @UlrikeFischer might be best to have a new script dvipspdf that can have whatever commandline options we need and controls the whole dvips ps2pdf pipeline then one less command for the user and we can control the whole thing
@UlrikeFischer I don't know, actually. But whith this kind of special we get it at the earliest possible location in the PS. In the linked spec they say that non-Adobe DSC comments begin with %!<vendor prefix of up to 5 chars>
@PauloCereda quack quack :) I grew uo with this in East Germany. And I like the voice a lot. The speaker hass passed away some years ago, though (at a high age).
@AlexG yes, I quite like this variant. We load a header file anyway, and in case we ever need different code for different pdf versions we could even use it for real code.
@AlexG A local supermarket recently sold super big stuffed animals of the characters. In the parking lot I saw a little boy carrying a Sandmännchen two heads taller than the boy himself. That looked so funny :)
Hi everyone, I am trying to figure out how can I ref a citation. \href{\cite{cite-identifier}}{text} gives TeX capacity exceeded, sorry [input stack size=5000]. Any suggestions?
@aeyalcinoglu the argumant to href has to be a URL, \cite isn't expandable but even uts typeset output is ususally something like [2] what do you want this construct to do?
@UlrikeFischer Hmm, I understand I wanted to have custom text for the \cite, any easy suggestions for that? I have [1], instead of having "As you can see in [1] ..." I want to have something like [As you can see ...], like href
@aeyalcinoglu the visible link text is the second argument to \href (you could use \cite there) the first argument is the URL to link to. But you have no URL here as far as I can see?
@DavidCarlisle The citation has a URL inside of it. But the behavior I want is simply \cite with custom text instead of [1], so that when the person clicks it, it goes to the citation.
@aeyalcinoglu the URL in the citation isn't releavant here then, you could presumably use the hyperref command to link to the bibitem id (so not \href) and then use the form of \cite that does not make a link, to avoid nested links.
@aeyalcinoglu you would need the destination name of the citation, which depends on which bibliography system you are actually using. So without small complete example no answer is possible.
@aeyalcinoglu because citations are in the core labels which should allow to identify a bibliography entry, this defines their content. An arbitrary link to a bib entry is something else.
@aeyalcinoglu well it won't be that complex, you just need to use the right commands so not \href, which would be like going <a href="see the item on page 2">??</a> in html. But it is unusual as latex cross referencing is built around \cite and \ref mostly, and they generate the link text (usually just a number)
@aeyalcinoglu yes exactly: you want hyperref not \href to reference an internal key. I am just trying to recall if there is a user syntax like \ref* to access the original no-link citation (obviously the original code is there)
Howdy, I require some assistance with some LaTeX issue that I am trying to solve. It regards the package of algorithm2e
Here's my relevant question and the MWE I've written for it: https://tex.stackexchange.com/questions/592519/align-algorithm-lines-on-the-equals-assignment-symbol
@AlexG well the best would be if dvips could handle open type fonts. We really should try to get this. But until then you need something like the following. luainputenc does something like this, but I don't know if it handles all the details, like bookmarks etc.
@DavidCarlisle I thought once to try to get rid of some of these patches like I removed the babel patches, but imho none of these packages (apart from revtex) are actively maintained, so it would be difficult to find someone to push ...
So, is there an alternative? Should I use a listing of a supported language (e.g., \lstinputlisting[language=c]{c.c}) and write the pseudocode of the algorithm there? Would that work?
@Broxigar it might if your pseudo code is sufficently c like but lots of peopel manage with algorithm2e or algorithmx or one of the pther algorithm packages. If something doesn't work as you expect make a test document and post a question on the main site, somome will answer.
@UlrikeFischer because journal blub doesn't allow it.
@Broxigar have you tried one of the more structured packages such as algorithmix? as you have it there is clearly nothing to make an alignment (you could put the lefthand sides into \makebox[3cm][r] so they were the same width but I'd avoid such explicit spacing, also don't write new and old in math ode, use \mathrm{new} and \mathrm{old}`
@PauloCereda I tried your approach. It works. I am playing with the command to try to reduce the rhs spacing as well. I've seen this {@{}p{1cm}ll} namely, the @ symbol being used in the tabular environment. What does it stand for?
@DavidCarlisle I didn't get the idea of putting the placeholder OutputFile as value of key /OutputFile into the setpagedevice dictionary. Great that you figured it out!
@UlrikeFischer the downside is that the PS then can't be used for anything else, also of course you could write the filename in instead of use OutputFile then you wouldn't need to pass it in again on the commandlline....
@DavidCarlisle and regarding the PS: if we create a dvipspdf script which combine the calls, then it shouldn't matter much, one could even clean it up.
@DavidCarlisle Yes, it is a texlive script, at least if one doesn't force the use of an external ghostscript. The gs call is a bit OS dependant (I had to use gswin64c), but beside this it should work.
@DavidCarlisle You can prevent non-ps2pdfwr devices (PS printers, PS viewers) from trying to execute this:
\special{!
mark
<<
/CompatibilityLevel 2.0
/OutputDevice (pdfwrite)
/OutputFile OutputFile
>> setpagedevice
systemdict /pdfmark known not {cleartomark} if
}
abc
\bye
@DavidCarlisle Good suggestion. But we need to prevent other file-based output devices from exploding, such as PNG, PCL etc. So my suggestion for refinement:
\special{!
systemdict /OutputFile known systemdict /DEVICE known not and {
<<
/CompatibilityLevel 2.0
/OutputDevice (pdfwrite)
/OutputFile OutputFile
>> setpagedevice
} if
}
abc
\bye
For example: gs -dDEVICE=png16m -sOutputFile=out.png -dNOPAUSE -dBATCH ks.ps
@enthu -- Probably minority opinion here. For many years I worked for a math publisher. When professional metal type composition became unavailable, many other things were tried. TeX is the first thing that came along that approached the quality and complexity needed to publish the existing line of math journals and books. To learn TeX, I was first required to learn emacs. This combination has been successful throughout my career. (cont'd)
(cont'd) Emacs is "in my fingers", and if I try to use something else with a radically different philosophy, I make so many mistakes the task is hardly worth undertaking. I don't participate in editor wars; use whatever fits your style and satisfies your needs. "Fitting your needs" is paramount, and all needs are not the same. I've worked in a "mixed mode" environment, and different people are comfortable with different tools, aiming for the same result. If the result is what is wanted, good.
