texstudio is ok now that I figured how to disable some of the annoying automatic highlighting it had. I like the autocomplete feature (wonder if emacs has that also). Saves me having to look up the correct syntax each time. Also figured how to do the live preview with it. This helps alot. I am now writing more raw latex on my own and using SW less and less.
may be even one day I will do everything in plain latex and not use GUI.
I had to remove the `\` before the ``, but now I can reproduce the result.
The cause is clearly the space in echo -n "${B}${i:1} ". If I leave it out I get no spaces at all.
TBH, I have the feeling this whole approach is awkward if you care about where the spaces are (for instance, double spaces are reduced to single ones). Technically, you need to check whether you are in the last iteration of for (dunno how) and not output a space in this case.
@StephanLehmke Hmmm, seems this time the backticks did not need to be escaped... Yeah I just figured that part out - I think I should be able remove it outside of this script. Thanks for your help.
@JosephWright The change in the comment is OK; but the flame about a name is just stupid. I'm under the impression that the user has several identities here.
I am citing "The Theory of Sound" by John William Strutt (more commonly known as Baron Rayleigh). How should his name appear in the author field in BibTeX? Currently I have:
@book{Ray94,
title = "The Theory of Sound",
author = "John William Strutt, Baron Rayleigh",
year...
@AlanMunn I'd seen a TUGBoat on this (don't actually seem to have the right issue!): not sure it's actually that good a plan as the biblatex experience is that the real devil is at the LaTeX level
@JosephWright Yes, that may be true. My first impression was that this would be a great interface to biblatex itself. I like the idea of the higher level abstraction that the templates provide.
@AlanMunn To me, look very much like the biblatex drivers but without the various hooks that allow for things like tracking citations (ibidem, ...). I've not looked carefully enough to be sure, and I'd welcome PLKs input
I'm running Debian sid and want to use TeX Live from CTAN. So I didn't install the Debian texlive-packages, but created a virtual local package with equivs. You can find the control file below:
Section: misc
Priority: optional
Standards-Version: 3.9.4
Package: texlive-local
Version: 2014-1
Main...
@JosephWright While re-writing chemnum for v1.0 I tested groups as it has options that logically belong to different components of the package. I now have options that can only be set with \cmpd (and similar commands) but not with the setup command (they are filtered with \keys_set_filter:nnn). I had the idea that I wanted to give a warning in case such an option is used with the setup command... since those are keys belonging to group A but not group B a conditional seemed a logical idea.
I am trying to typeset a structured proof
as demonstrated by Leslie Lamport in his paper
How to Write a 21st Century Proof.
In particular, I am trying to typeset Figure 3 (shown below).
My code and the output is shown below.
\documentclass[12pt,letterpaper]{article}
\usepackage{amsmath}
\use...
I wanted to ask question on main board, but thought to check if it makes sense? how does one measure the quality of the pdf file generated by pdflatex from same source, but on 2 different platoforms, or on same platform, but using different texlive versions?
I am asking, because I think the pdf file I am getting is not good. i.e. does not look sharp as it should be, and the quality I think should be better. But have no way to quantify this.
here is an example: Same sources, one build using miktex 9 on windows, and one build is texlive 2013 on linux. one pdf file is little larger than the other
@Nasser It sort of makes sense but almost certainly the difference in pdftex version is not the issue as the differences are so slight. More likely you are picking up different fonts, use pdffont utiility or the acrobat font menu and check what you have
@DavidCarlisle thanks, but even if I figure how to use this utility and it tells me some font names, I would have no idea what all this means. I was looking for some simple one number to use, to tell the difference in "quality" between the two files. But may be there is no such thing. Will try pdffont now and see what it says.
sometimes also the screen resolution also can cause the pdf file to look bad, but when it printed it is ok?
may be there is a pdf diff tool! will look into this.
So, this happened: Fuzzy the number of questions in the close review queue, a dopamine for the shutterers
Now, only questions with at least 4 votes/flags are listed in the close review queue. If you're thinking, "that's crazy!" THEN YOU'RE RIGHT! This dramatically reduces the utility of the queu...
@DavidCarlisle i've run pdffonts on the 2 pdf files (one by miktex and one by texlive). I put the resulting 2 lists in this text files here 12000.org/tmp/fonts they have same number of lines (so same fonts) and counted same type 1 fonts in both.
so looks like same name fonts are used on windows (by miktex) and linux (by texlive).