@JosephWright wow, working on dvips. I wonder if it is worth to ask about better support to add something to the page resources, I currently have no idea what to do there.
@JosephWright also you can add something to the page dictionary with \special{ps:~[{ThisPage}<<--->>~/PUT~pdfmark} so the resources sub dictionary should be possible too. One only need a name for the object.
@JosephWright can you? I'm not sure if I know enough about the postscript to be able to ask about a sensible special to get something in /ExtGState and /Properties etc.
@JosephWright yes, I guess it should be in the page. But that is not the question with dvips, the question is how to get something in the dict at all. Or do you know code for it? The transparent package doesn't work with dvips, so I guess Heiko didn't find something or it was too complicated.
@JosephWright there is transparency mentioned in the pdfmark manual, and there is an example tex.stackexchange.com/a/199791/2388 (but it doesn't work for me currently), but I didn't find anything about other resources like Properties or ColorSpace.
If you want a symbol, use \mathcal:
\[
\mathcal{E}=-N\frac{\Delta\mathnormal{\Phi}}{\Delta t}
\]
If you prefer “emf”, then it should be in italics like every other variable name:
\[
\mathit{emf}=-N\frac{\Delta\mathnormal{\Phi}}{\Delta t}
\]
Full example:
\documentclass{article}
\usepackage...
@Sebastiano If you look at the wikipedia page, a bit down you find “or a tightly wound coil of wire, composed of N identical turns, …” followed by the formula with the N included.
@UlrikeFischer Transparency, as defined by the PDFmark documentation is not supported by Ghostscript, only by Distiller. Ghostscript has its own, dot-prefixed set of .<commands>. It would be useful to implement both and select the pertinent one during runtime, evaluating the result of the product PostScript command.
@AlexG pstricks seems to support both. Also Herbert just told me that it works with ps2pdf if you use the -dNOSAFER switch and this is true (also with pgf). @JosephWright
@AlexG but my main problem is how to handle the interface to the page resources at all. E.g. what to do with /Properties? Is it possible to get something backend independant?
@UlrikeFischer Transparency-related modifications to /Properties etc should be done automatically by Ghostscript/Distiller. Doing so manually may break something.
@UlrikeFischer Yes, the <<property list>> associated with the BDC pdfmark is automatically turned into a PDF object and referenced in the /Properties dict of the page. The /Name associated with the object reference is also automatically generated by ps2pdf/Distiller.
@HaraldHanche-Olsen Meanwhile I thank you very much for the link. I think, but I'm going to remember, I saw that N when I studied the coefficient of auto and mutual induction. My most cordial greetings.
I tried to install teXlive on my laptop running Windows 8.1.
After unpacking, I ran "install-tl-windows.bat". It seemed OK for most of the installation, but then I got this in the terminal (the log file is the same):
Installing [2321/3058, time/total: 01:06:55/01:24:53]: qsymbols [136k]
Installi...
@EnthusiasticEngineer If you have the space it is always possible to install the new one without uninstalling the old one, and just delete if you decode later you never need to go back. (I know that doesn't help you now but...)
@EnthusiasticEngineer well that depends. If you are using pdftex then for 99% of documents a texlive from 2000 will work fine but of course if you happen to hit a bug in a package and someone tells you it was fixed earlier this year, they are more likely to tell you to update than tell you how to patch an old release. If you are using luatex, I'd recommend always having the latest release, there were a lot of changes and fixes in recent years
@EnthusiasticEngineer some of use (@JosephWright, me, @UlrikeFischer ...) have to have the latest release as we are working on the next release, but we are not typical users:-)
@UlrikeFischer I don't know exactly how these are defined. But in any case, for dvips, DON'T provide hooks for manually adding to /Resources or to its /Properties sub-dictionary as it will break OCGs and XObjects. Ghostscript's .setopacityalpha and friends as well as Distillers transparency related pdfmarks do the necessary insertions automatically without breaking things. @JosephWright
@AlexG well that's certainly wrong: you get a second resources dictionary and this will break lots of things. The question is if one need a way to add something to one of the entries of the dictionary.
@DavidCarlisle wasn't it part of the fp documentation that units are accepted and converted to pt. Is this about to change?
@JosephWright is there any way of joining two coffins and somehow keep the handle of the first coffin which was used at the same place while still enlarging its bounding box?
@Skillmon yes and no it did change a bit but only changing the priority of the way things were bound due to a question here where the unit didn't bind as tightly as you might have expected and Bruno adjusted it a bit. (Personally I'd have banned them if I could have gone back in time to prevent existing use:-)
@Skillmon yes but it acts as documented not as a real dimensioned expression so cm is really just a floating point number and juxtaposition is multiplication so (1cm)cm is valid as is 1cm*1cm but it's not as if fpeval understands areas or volumes etc
@UlrikeFischer @JosephWright Btw, a similar problem is writing to sub-dicts of {Catalog}. Pdftex, for instance, provides \pdfnames. For Dvips, the only way would be [{Catalog} /Names <<.....>> /PUT pdfmark. But this would zap existing entries in /Names, such as /Dests (automatically inserted and populated by the /DEST pdfmark.)
@AlexG the question is what is needed, what must be public, which ugly details should be hidden. For /Properties e.g. you populate them in dvips through BDC and I think that could done in the other drivers too and the direct access can be hidden. /ExtGstate could work similar, if I can find out how the transparency works.
@AlexG do you have an use case where using \pdfnames is actually needed?
@DavidCarlisle /APPEND appends to Arrays. /PUT appends to Dicts. The actual problem is the destination of the operation. You need a symbolic name (predefined, such as {ThisPage}, {Catalog}, or a user defined one).
For the majority of global or page-related objects such predefined names do not exist, unfortunately. One could add a completely new sub-dict to the parent dictionary for which a predefined symbolic name is provided, but this deletes/overwrites an existing sub-dict of the same name. As shown in my example above.
@DavidCarlisle The implementation status of pdfmarks in Ghostscript is not that bad, actually. Some desirable operations are just not possible, with both Distiller and Ghostscript.
@UlrikeFischer Transparency is implemented in Ghostscript with <opacity val between 0...1> .setopacityalpha, in Distiller with [/CA 0.5 /ca 0.5 /SetTransparency pdfmark (alpha for stroke and fill set separately). Both methods add ExtGState automatically.
@UlrikeFischer AlexG may provide something more specific but you can always do /.setopacityalpha where {(gs) ==} {(distiller) ==} ifelse which echoes gs if .thing is defined and echoes distiller otherwise
@JosephWright -- Whatever is done has to work with "Knuthian" tex. Tom is giving a talk on this at the TUG meeting. You might prime Frank or Chris to be prepared to ask questions.
@DavidCarlisle uff, no more special backend formats ;-). But this all sounds as if ExtGState should better be handled on the "draw" level in commands handling transparency (and as special case overprint, \special{ps:true setoverprint}) and not by direct access @JosephWright.
@UlrikeFischer that isn't a special back end, it would just be valid ps code for dvips to insert if it doesn't know what ps to pdf system was following
@UlrikeFischer @AlexG's known operator is doing the same thing as where here (but probably a bit more efficiently) either way you get false if the command isn't defined.
@AlexG oops still close enough (I wanted to use known but I couldn't remember the dictionary it would be in:-) I don't think I have written any PostScript since the 1990s
known directly asks if the command is defined in systemdict returning true or false, where searches around and returns a dictionary where the name is defined and returns false if none is found. So since "we" know we want to look in systemdict that's better
Microsoft released a new Windows 10 Insider Preview build this week featuring the Windows Subsystem for Linux 2. WSL 2 includes a real Linux kernel that lets you run more Linux software on Windows and with better performance than WSL 1. From a report: This is part of Windows 10 Insider Preview build 18917, released on June 12, 2019. It's part of the fast ring of updates. You can experiment with it today, although you'll have to join the Windows Insider program and get unstable builds of Windows 10 on your PC. Microsoft's Windows Command Line blog offers more information about WSL 2, complet…
@JosephWright with page resources access I would know too, the question is where is the "indirect" way like for /Properties (through a BDC mark) and /ExtGState (at least for transparency and overprint). I could ask Herbert, he knows it perhaps.
@UlrikeFischer As far as I can tell, ColorSpace is entirely set via the PostScript setcolorspace command. No need to meddle with /ColorSpace in the page dictionary. Distiller adds it automatically and Ghostscript makes the settings completely inside the content stream: Here is an example:
quick poll: in code comments(any programming language), text content (tex, markdown), or in any language where you break lines at a certain character count
@Lacey -- When I'm creating a file, I usually end up with something that looks like style 1. But if I have to edit a file, I really prefer style 2. (So clearly I should be more observant when I'm creating files, so they'll be easier to work on later.)
@Lacey I hate style two even though it's much more sensible for version control systems. It's just very awkward to get into the habit of writing that way.
@Lacey Definitely style 2, for the reasons given by @barbarabeeton. Also, in a big paragraph, it makes it easier to find a sentence in the source. The line breaks in the source and the typeset output will not match anyhow. And for version control, too. Cleaner/clearer diffs, that is. But it takes some getting used to writing that way. (I write that way for HTML too.)
@yo' -- I don't remember any special way of presenting C++ and can't find anything in the AMS style guide. I'll ask. (My inclination is that the pluses should be smaller than the default cm versions and sitting on the baseline, but actually checking would be good.) Re "difficult tasks", wouldn't have asked unless we thought you could do it well. (Sorry to cause angst though.)
Hey, I just read that user Mico decided to delete his profile! I hope that is will not happen (tex.meta.stackexchange.com/questions/8025, last comment on question).
@yo' Isn't "standing up" what you just try to do here? You disagree with my opinion (which I feel you do not necessarily understand, possibly due to language barriers) and/or behavior, and comment on it, even though this is not directly your concern. I think this is standing up.
@marmot As I said, I do think that it is your right to automatically ignore such users. What else it is other than saying that Mico's suggestion is not righteous?
@DavidCarlisle thank you david. I had downloaded the iso file from a mirror which was located inside the country. Now I downloaded from an international mirror and the installation is going forward.
If you want a symbol, use \mathcal:
\[
\mathcal{E}=-N\frac{\Delta\mathnormal{\Phi}}{\Delta t}
\]
If you prefer “emf”, then it should be in italics like every other variable name:
\[
\mathit{emf}=-N\frac{\Delta\mathnormal{\Phi}}{\Delta t}
\]
Full example:
\documentclass{article}
\usepackage...
