Hot answers tagged

32

Personally I don't think it's our place to be policing supposed use of unlicensed anything unless the question is about how to get the fonts illegally or circumvent the licence in some way. I especially don't think we should be making assumptions about where people got their fonts from if they are asking an otherwise legitimate question. So questions ...


22

Header: Palatino Linotype Text: Lucida Grande Code text: Consolas At least that's what computed CSS says (accessible in FF via Right Click -> Inspect Element -> Right Bottom Panel -> Computed -> font-family). However: Do not use web fonts for printed articles. Do not use web fonts for printed articles. Do not use web fonts for printed ...


18

The unannounced change should be reverted as soon as possible. I would even remove boldface from the current tab name, normally active, because the rule under the tab name is sufficient. Boldface is a device to be used very sparingly, because it catches attention: with the current setup, tags are more prominent than question titles.


16

I see a few issues. As has already been mentioned in a comment, CM is rather 'light' on the screen: Knuth allowed for the bleed in printing when designing the font, but that makes it a not-so-good choice on screen. More generally, I feel that sanserif fonts probably work better, particular on smaller screens. Secondly, the 'LaTeX always uses CM' approach is ...


15

Honestly the SE sites have generally very good designs and very nice choices in regards to how things appear, but the tag change is really a punch in the eye. The tags now are as black as the text, making them virtually indistinguishable from the text at a first sight. I'll just say this: Using bold for everything is like using the highlighter pen for the ...


14

I think the main site looks a little bit silly now. In the following screenshot, the things encircled in red need to be bold as well. The content of the blue circle needs to be super-mega-bold to fit again. Just reverting the bold tags to normal would be easier and better, though.


13

We tracked down the bug. The Tex community has a few special classes for text formatting and those happened to conflict with a recent mixin that was added to a global file. The change was unintentional and an update is rolling out soon. Thanks for the catch and your patience.


11

We have a couple of methods for dealing with the problem: commenting; editing. A comment could be something like Please edit your question, because, as it's formulated now, it can raise some doubts about copyright issues. On the other hand, how the questioner came in possession of the fonts is usually not relevant for solving the problem, so an edit ...


10

It seems I’m only able to post answers and not comments, sorry about that. When using derivatives such as XeTeX or LuaTeX, specific font tags can be very useful since the OpenType (or other) font features may vary from font to font. For instance, questions such as “How do I get real superior text in font α?” or “Contextual alternates in font β” would be ...


10

Surely you're seeing something we're not. Here's an image of the votes and view count font on my system (Firefox 10.0 on a Mac): I really don't see how the 4 and the 2 are very similar, and although the font is serifed it doesn't seem very baroque to me (although obviously this is a matter of opinion.)


10

It's indeed HUGE. I changed it from 45px to 120%. The change will be on live after the next production build.


9

I have increased the line-height in comment section slightly so the code and owner blocks don't overlap. The change will be in the next production build.


9

This seems to be an OpenSuSE bug: https://www.tug.org/pipermail/tex-live/2011-January/028355.html


7

This is what I'm seeing (with FF10 on OpenSUSE 11.3 with KDE):


5

There's a difference in the colour of the tags. Here's a screen grab from the "legend" on the tags page: {required-tag} has RGB = (68,68,68) {tag} has RGB = (85,85,85) However, this is too close to discern when both are bold. For example, on Meta.TeX.SE one is required to have one of the four tags bug, feature-request, discussion or support which are one-...


3

This looks particularly ugly on Firefox 43.0.4 on Ubuntu 14.04, in my opinion. There is a lot of extra space around the name of a tag and the { and }.


Only top voted, non community-wiki answers of a minimum length are eligible