| bio | website | sampablokuper.com |
|---|---|---|
| location | Cambridge, United Kingdom | |
| age | 93 | |
| visits | member for | 11 months |
| seen | 11 hours ago | |
| stats | profile views | 31 |
Interested in web standards, semantics, communication, history of science, and the - uh - universe...
|
Apr 11 |
comment |
(Why) did the Gyre project fork the URW fonts rather than just extending them? @KhaledHosny, since the aim of the Gyre project was, IIUC, to extend the URW fonts with diacritics/etc, why would the existing characters not remain metric compatible with the URW fonts? |
|
Apr 11 |
comment |
(Why) did the Gyre project fork the URW fonts rather than just extending them? @MartinSchröder, in what way are they "not simply extensions"? As for the intellectual property issues you hinted at, please could you be more specific? Does the license disallow the use of the original font names? |
|
Apr 10 |
revised |
(Why) did the Gyre project fork the URW fonts rather than just extending them? added 46 characters in body |
|
Apr 10 |
comment |
(Why) did the Gyre project fork the URW fonts rather than just extending them? @JosephWright do you mean that the Gyre project folks thought the presence of "URW" in the names would have been incongruous in the sense that it might cause people to mistakenly believe that URW++ was responsible not only for the initial set of glyphs but for the whole set of glyphs (i.e. including the diacritics/etc that the Gyre project was intending to create)? |
|
Apr 10 |
revised |
(Why) did the Gyre project fork the URW fonts rather than just extending them? added 54 characters in body |
|
Apr 10 |
asked | (Why) did the Gyre project fork the URW fonts rather than just extending them? |
|
Mar 18 |
comment |
Ligatures in Hoefler with XeTeX? See also: trac.macports.org/ticket/28497 |
|
Mar 18 |
comment |
Ligatures in Hoefler with XeTeX? In case it helps anyone: I achieved this by uninstalling all installed ports, and then running sudo port install texlive-bin +atsui +x11; sudo port install texlive +doc +medium; sudo port activate texlive-bin @2012_5+atsui+x11 . That worked for me (and gave me proper ligatures in Zapfino, and let me use alternates as per tex.stackexchange.com/q/33855/15911), but there may well be a quicker way :) |
|
Jul 6 |
comment |
Why are bent arrows with arrow tips not symmetric in TikZ? Not an answer, but have you considered using XY-pic? Its syntax for drawing small diagrams like the ones in your examples is much more concise than TikZ's, and I think its curved arrows are symmetric (although I haven't looked closely). |
|
Jul 6 |
comment |
Ensure verbatim code block is copy/paste-able If it seems weird, that's probably because we've been working from different assumptions. My approach is that this is all just software, so any computationally feasible result should be possible; but that if for some reason PDFs or TeX are limited in a particular way that makes what I am asking for (i.e. genuinely verbatim text blocks) strictly impossible, then a knowledgeable user here will point out this limitation and explain why it is insurmountable. Unless that happens, I remain optimistic. |
|
Jul 5 |
comment |
Ensure verbatim code block is copy/paste-able Other than PDF: certainly. PDF by tools other than TeX: maybe, but I haven't checked. |
|
Jul 5 |
comment |
Ensure verbatim code block is copy/paste-able @DanieEls if I already knew how to do all that, I wouldn't be here asking how to do it :) |
|
Jul 5 |
comment |
Ensure verbatim code block is copy/paste-able (Specifically, using the native feature - i.e. the verbatim environment - which is ostensibly for this sort of purpose.) |
|
Jul 5 |
comment |
Ensure verbatim code block is copy/paste-able It isn't stretching it far at all. Loads of document formats are capable of being viewed on a range of platforms and of representing text verbatim in a manner that also allows verbatim copying and pasting. I'm merely asking how to achieve that with this one. |
|
Jul 5 |
comment |
Ensure verbatim code block is copy/paste-able @StephanLehmke my point is that other than using a monospaced font, LaTeX does not seem to be typesetting verbatim environments correctly. I.e. it is treating them as though various normal typesetting rules apply, when in fact they don't. My question can be restated as: is there a way to tell LaTeX to apply only appropriate typesetting rules to verbatim environments? |
|
Jul 5 |
comment |
Ensure verbatim code block is copy/paste-able @StephanLehmke The whole point of a PDF is to be, as its correct name suggests, a portable document format. There is no need for the output of the verbatim environment to be a "microtypographic result of a complex rendering process": it needs to do little more than pick a monospaced font and a starting co-ordinate, and then lay the characters down in sequence. For a document containing dozens or hundreds of code snippets closely referenced in the text, it would be maddening if they were provided as attachments instead of as code blocks. |
|
Jul 5 |
comment |
Ensure verbatim code block is copy/paste-able @JosephWright I appreciate that TeX is a typesetting system aimed primarily at print output. However, (a) it is neither novel nor esoteric to read PDFs onscreen instead of as printouts (especially in contexts like computer system tutorials where dozens or even hundreds of code snippets are to be copy/pasted), (b) LaTeX should facilitate the creation of suitable PDFs, and (c) I think perhaps you are forgetting that I'm talking about the verbatim environment rather than about flowing or body text; I totally appreciate that in the latter context, normal typesetting rules apply. |
|
Jul 5 |
awarded | Nice Question |
|
Jul 5 |
comment |
Ensure verbatim code block is copy/paste-able Copying and pasting from your PDF (as viewed in Safari 5) to TextEdit yields a completely unusable result, I'm afraid. |
|
Jul 5 |
comment |
Ensure verbatim code block is copy/paste-able Thanks. This doesn't really answer my question, but it might help people who are using the "listings" package. |