Hi Tex Gurus, I have a document set using mathpazo. Now I have code listings I want to include using minted, that contain unicode characters like Π or ⦃. 1.) Can I set them nicely in a TT font without using xelatex? 2.) If I'll use xelatex and fontspec, can I somehow prevent the rest of the document from using TT or OT fonts but instead stay the same as what it looks like now? I'm not very satisfied with the appearance of several OT alternatives I tried.
@PauloCereda yeah. Let's stick to frisbee for a while, there's not much money involved. But once it gets spoiled, we'll have to find yet something new.
What is the recommended method of getting footnotes at the bottom of the page when using \raggedbottom? I have a long standing request for memoir to implement that. And I'm finally going to have a look at it. There is the fnpos package which seems to do what is needed (and is very simple). So I'm just asking is there is a preferred method of doing is and whether there are classes already providing this (which one can get inspiration from)?
@daleif well, it makes sense to me, after all... Just you probably should just use the code, not the package, so that you have control over what's going on...
@DavidCarlisle as far as I remember there are some elements in it that are not compatible with memoir (I usually never use it). But perhaps I can get som inspiration from it.
@yo' the code part of fnpos is 40 lines ;-), but it is also from '99 so there might be things missing (which is why I'm asking), for example things from fixltx2e?
@daleif @DavidCarlisle @yo' not sure I'm awake already, but rather than changing the OR code couldn't one simply change \skip\footins to contain some "filll"?
@FrankMittelbach running a ctan build here to check before checkin in but I think I've done the reference to gnats in headers, also plan to change ...{base} in the maintainedby banner to ...{LaTeX} (since that's what the gnats for requires, that OK?)
@FrankMittelbach true but that's why I decided it wasn't worth going to the office. It's been "croaky" all week but this morning It's basically not there at all,
@FrankMittelbach yes, needs to be lowercase, I'll let the build checks finish though now as they are three quarters through, then lc them.
@JosephWright I did a build ctan a few minutes ago, just doing another now for checking "can't go wrong edits" like 2014->2015 but if you push yours to dropbox that's probably safest.
A user very kindly posted a solution that almost work, but there is a problem with ambiguous header names being uniquely labelled by the pgfplotstables package in an undesirable way
Hi guys, I'm using utf8 input encoding and I have minted code listings using unicode and Ubuntu Mono as a Font. Ubuntu Mono actually has quite a lot of characters, but nevertheless symbols like ⦃ are only shown as boxes. What am I doing wrong? Do I just have to convert my files to UTF16?
@javra if you are using pdflatex rather than xetex you need to find a font with those characters in positions 0-255 (or re-encode an existing font so that is the case)
@TorbjørnT. ah, that's unreliable, but fine if it's not crucial. It should work, probably (I dunno, my local Sage install opens some external program for 3D drawings
@Johannes_B No Problem. Just wanted to set the link in comment... To have the fix at hand and to offer the issue tracker for other users/future problems...
I'm trying to typeset a document using minted code listings that contain quite some amount of non-standard Unicode characters. I'd like to use Ubuntu Mono as a monospaced font. The following supresses unicode characters:
\documentclass{book}
\usepackage{minted}
\usepackage{fontspec}
\setmonofont...
@Johannes_B it is a part of the latex design that you can use any command as an environment, so depends what she's demonstrating, is she demonstrating that?
@Johannes_B although you have to be careful about spaces as @yo' is hinting, but that bad space comes from the white space in the input, not the environment syntax
@yo' not really. It's a simple rule that box commands like minipage, parbox, scalebox, mbox,... have no special spacing behaviour, they are just spaced like X
@Johannes_B they need to be used with care but that have their uses, especially for a long run in a custom font, using \begin{bfseries}.... \end{bfseries} makes the end a lot clearer than a stray } several lines later
This question still doesn't have an answer, although it was answered in comments and in the question itself. I will post the answer here, because duplicate question was posted today and it can't be closed as duplicate as long as this question doesn't have accepted or upvoted answer.
This issue w...
@JosephWright I figured out that he is right, string {?nl} is used in place of new line in the svg file, but it is not displayed, so you can't see it unless you inspect svg source
@DavidCarlisle -- so i do. fast work, sir, you who talks about the "one with the prrof reading corrections." (but somehow you manage to spell your control sequences correctly. hmmm.)
My \myhrule for rules in headers looks slight different than David's. The position of the heading text doesn't depend on the depth of the text. And, of course, I needn't any additional package.
\makeatletter
\def\myhrule{\lower1ex\null\vadjust{\hrule}}
\renewcommand\ps@headings{%
\def\@evenhea...
@DavidCarlisle Is it different from your first answer?
@egreg I didn't realise it did that! But I still think obsolete packages should be dropped from TeX distributions. Most users don't bother to keep track of package changes and carry on using package foo year after year without realising that it's obsolete until things go wrong and people say, why on earth are you still using foo, that went obsolete years ago.
At least this way it draws users attention to the fact that the package is obsolete. They can then download the obsolete package from CTAN with the full knowledge that it's obsolete.
My .tex file, I'm pretty sure has become a binary file. It begins with this:
\%PDF-1.5
\%ÐÔÅØ
6 0 obj <<
/Length 1662
/Filter /FlateDecode
>>
stream
and there's a lot of odd symbols. I'm using TeXstudio to compile my documents and when I click the 'view' button I get the document as it l...
@Johannes_B Leslie Lamport has \begin{em} ... \end{em} in "LaTeX a document preparation system". I think if something's in the user guide and reference manual it's a fairly safe assumption that it's part of the system's design.
@NicolaTalbot although white space can be tricky to handle (or at least tricky to remember to handle) in that form, especially for size change commands
@DavidCarlisle Yes, this is true. White space often trips people up (which is why I decided to put a note about it in the introduction of my new LaTeX book).
@egreg But it's still on CTAN. The missing package error alerts the user that something has changed about the package. The user looks it up, finds out it's obsolete and can download and install it on ~/texmf or wherever and it remains there untouched by TL but the user now realises it's obsolete.
@Johannes_B In most cases you only need to change the font for a small selection of words in which case it's easier to just use a text-block command like \textbf.
@AndrewCashner I've noticed that many users tend not to look at the transcript. In fact, some users don't even appear to pay any attention to error messages either and just run LaTeX in batch mode.
@Johannes_B Yes, but even if you do, say, \newcommand{\keyword}[1]{\textbf{#1}} it's still easier than \newcommand{\keyword}[1]{\begin{bfseries}#1\end{bfseries}} but if you're designing, say, a class or package that prints some boilerplate text in, say, a small font it then might be easier to use a declaration or environment.
@NicolaTalbot yes although users have forgotten how to install packages as it is required so rarely, and it's a bigger headache for things like arXiv it means that have to never update or keep track of which extra packages they need to add back after updating. (arXiv is big enough it may just record which tex distribution it used) but generally document repository management is harder if packages go.
@DavidCarlisle @egreg @yo' @PauloCereda I thank the TeX community & each of you in particular in the acknowledgments of my PhD dissertation, which I defended on the 11th. Now if you need any music doctoring you know who to call.
@DavidCarlisle But TL just gets bigger and bigger every year. When I first bought my computer I thought 2TB was ample and with the standard percentage split between the partitions there should have been plenty of space on /usr/ etc for applications and /home/ for all my stuff including some extremely large image files. TL2012 fitted on /usr/ but TL2013 didn't so I've had to move it to /home/. It's going to get to the point where I'll need to buy a hard disk just for TL!
@NicolaTalbot hard disks get bigger faster (hmm except when I switched to ssd and it got smaller;-) But I've only ever tried to remove two of my packages from ctan, and they both came back. (admitedly that was remove from ctan not just from TL)
@DavidCarlisle Thanks! I wanted to ask you about XML. For the diss LaTeX was ideal because I am basically self-publishing a PDF. For future work (articles, books) I want a highly portable, fully semantic format so I can send things to publishers in whatever format they desire. Is TEI XML the way to go?
@DavidCarlisle :-) I'm evidently going to have to sell a lot more books to keep up with the hard disk requirements for TL! But I do think it's the only practical way to alert users to the fact that they're using obsolete code otherwise they only find out when they encounter an issue with some conflicting package and they get told "why on earth are you still using foo.sty?"
@NicolaTalbot Sorry, but it doesn't work. The good thing you could do is to add a big warning to datetime. Some people will continue to use it nonetheless, but savvy people will understand and switch.
@NicolaTalbot Recall that some people can only install a distribution provided TeX Live (say they are in a strictly controlled environment where they aren't allowed to add packages other than the Debian provided).
@NicolaTalbot I used bibleref throughout (my work is on religious music so there are a lot of Biblical citations). I only wish you included a full list of the abbreviations in the documentation.
@NicolaTalbot Sorry, but it's your position that doesn't make sense. A user who has a document written three years ago, suddenly finds it's not compiling any more. Recall that many people use LaTeX as an archival format.
@NicolaTalbot And what about somebody who must use several machines?
\documentclass[a4paper,12pt]{report}
\usepackage[paper=a4paper]{geometry}
\usepackage[draft]{hyperref}
\begin{document}
\begin{figure}
\centering
\includegraphics[scale=0.5]{graphs/power.eps}
\caption{test}
\label{fig:power}
\end{figure}
\end{document}
I used the linux command ...
@egreg I have documents dated back to LaTeX2.09 that contain packages that are on CTAN but not on TL. I'm not going to get angry that I have to fetch those packages from CTAN when I decided to recompile them.
@egreg Well, that will be very nice of people to do that after all the years I've spent writing free code that I could've chosen not to distribute.
@NicolaTalbot yes so do I, but we don't count, most users don't write latex books, or don't write latex. It's not going to be clear to most people when documents fail that a package not available vial tl or miktex update is in fact on ctan somewhere. There's a reason we still distribute slides.cls:-) If you are worried about space how much would a package giving the old interface with the new code take (like epsfig which matches the old latex2.09 package, but is just a simple wrapper around grahics)
@AndrewCashner It depends, like any other form of communication, it helps if you use the same language as the people you are communicating with:-) In the mathematical/computer science areas I was in when working in those areas, that meant latex, there are areas of the humanities where TEI (and the oxygen editor) seem to be taking over, I'm not really an expert on TEI but its strengths (as I understand it) are annotating xml forms of existing manuscripts.
@egreg I never understand the sense of fancyhdr. When I have the "input point" to the output routine in the form \headline or something similar and I know the \hbox \vbox arithmetic then I don't need any more.
@AndrewCashner and I know nothing about Music requirements for academic publishing:-) Basically I'd use latex if you are used to it but write it in a form that can be easily dumped to something else...
@wipet but you don't understand the point of latex either so that's consistent
@wipet your comment about latex colour being complicated compared to the simple plain headline being typical, yes the plain one is simpler but it only works in simple cases, if you want colour to break over a page without leaking into the headline, you need some groups and colour settings in the headline, so the simpler plain version is just an illusion.
@DavidCarlisle In musicology everyone except maybe six people uses MS Word. Oxford University Press, Univ. of Chicago Press, both ask for manuscript submissions in Word format. So whatever I do has to be convertible to Word, but for my own sake it also needs to be in a plain-text source and can be used with free/libre software. I tried to make a TEI document but couldn't do anything with it without knowing XSLT. Maybe keeping my LaTeX semantic and simple and using tex4ht would be easier.
@AndrewCashner to be honest I probably wouldn't use general convertor such as tex4ht or latexml, for an internal document recently submitted in latex I just wrote some custom perl for the subset of latex really used, if the latex is well structured you can get simpler cleaner html than a general convertor can get, and its easier (without knowing the details of tex4ht etc) to drop in special convertors (such as listings -> pygments in my case) but if a general convertor to word works, that's fine too
@AlanMunn but since you are picking up with *-crop.pdf there won't be any path component so for f in *-crop.pdf; do convert -density 600 "$f" "${f/.pdf/.png}"; done
@DavidCarlisle The error I get is : `syntax error near unexpected token `convert' /Users/alan/bin/crop-png.sh: line 4: ` convert -density 600 "$f" "${f/.pdf/.png}";`
My \myhrule for rules in headers looks slight different than David's. The position of the heading text doesn't depend on the depth of the text. And, of course, I needn't any additional package.
\makeatletter
\def\myhrule{\lower1ex\null\vadjust{\hrule}}
\renewcommand\ps@headings{%
\def\@evenhea...
\documentclass[a4paper,12pt]{report}
\usepackage[paper=a4paper]{geometry}
\usepackage[draft]{hyperref}
\begin{document}
\begin{figure}
\centering
\includegraphics[scale=0.5]{graphs/power.eps}
\caption{test}
\label{fig:power}
\end{figure}
\end{document}
I used the linux command ...
