Hot answers tagged

33

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 ...


30

It's not really an answer, but my thoughts are too long for a comment. :) First of all, I'd like to thank you for all the effort you've put into moderncv and the time spent in helping people here. :) I really share your worries on some MWE lacking the minimal component. Indeed we have quite a bunch of such examples in our community. I once stumbled upon ...


29

They can be reported on Meta Stack Overflow - ZQNA was already added by @doncherry: Report sites that use SE content without following attribution rules here


28

After some discussion in the chat (link) I guess I can re-formulate the answer: Case 1. User clearly knows that it is a bug. Then the question should be closed as not a real question. Case 2. User is not aware it is a bug. Then he really wants to find a solution. In such case, I believe that the answer: This is basically a bug in the package/program and ...


25

It seems to me that the practice may have outstripped the previous consensus. I understand that (as the original meta question posited) a question that is a bug report should be closed. Truly that is not because it is "too localized" but because it is not really a question: "I've found this bug" is a statement, not a question. The question "Why am I seeing ...


22

We vote anything and everything. We are full of contradictions. If we somehow get what the point is we leave it alone unless it's really boring and unlikely to be done in finite amount of manhour x time x etc. That is another contradiction right there. We have monthly(biweekly?) Answer the unanswered sessions where we sweep the unanswered questions so most ...


21

I must say; I started with TeX a bit over a year ago. I found out about Stack Exchange a few months after that, very much a newbie still (Heck, in many ways I still am.) I found Stack Exchange to be the single best place, bar none, to get help with basic questions; the answers were complete, they explained why things should be done this way, they explained ...


20

Bug reports about (La)TeX packages etc. should not be posted on this site, but reported to the package author using the method (e.g. email address, bug tracker) given in the package manual. Because the bug might be fixed in the next version of the package, the "question" is IMHO "too localized" in time and should be closed as such with a note that bug ...


19

I would propose the following: If the question is asking for a way to do X, and it turns out that X can only be achieved by adding a new feature to a package (or using some undesirable workaround), an answer to that effect should be posted, asking the OP to file a feature request on the package site and edit the answer to include a link to that feature ...


18

It's not a problem. If there would be upvoted answers, the question would not be unanswered and would go away from the "unanswered" list. No need to close, what would actually prevent further, possibly even better, answers. See on the main meta site: Would it be possible to have a “community accepted” feature? You can show your acceptance of an answer by ...


17

I'd find it hard to say when this should occur. A popular answer might turn out to be too special or even erroneous much later, so its less popular sibling might be the only survivor. Also a not so popular answer might become more useful when the application of a question broadens by linking duplicates to it. So, personally, I'd say an answer should not be ...


16

There's no formal policy since, of course, you can't force people to use it. With many people familiar with this habit, most packages/classes are written using <code>. And, if not, they may be edited to "conform" to this. One advantage of using an alternative <code>-markdown is that it clearly highlights when you're using a package rather than ...


14

In general, the site is intended to work as a community, so using your votes is the preferred way to push for closing. Flagging is best used for things that really need moderator attention, which is more likely to be true for older questions which might not attract other people's interest than for very recent posts that will (probably) get other close votes. ...


14

One man's bug is another man's feature... I don't think whether the OP considers it to be a bug is that relevant. If the problem has been identified and fixed by the package author in an updated version of the package then we can consider treating the question by some special mechanism for "bug reports" otherwise it is best to assume that it's a permanent ...


13

Quoting from Joel Spolsky's answer: Why is there a green Honda Civic parked out in front of my house? This is too localized because: Who cares? Is it even still there? Go check. What are the chances that this question could ever be answered in a way that would benefit anyone else? Now is it there? In order not to be ...


12

In the case at hand, you simply couldn't delete you answer unless the OP revoked his acceptance before. IMO, you also shouldn't delete it because it shows an alternative approach that may be useful for other users (who may face not quite the same, but a similar problem in the future). "Disciplining" yourself rather is a proper course of action if you and ...


12

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 ...


12

Observation: Time has shown that the site welcomes both "elitists" and their questions (some users have great (La)TeX knowledge and they still ask very interesting advanced questions themselves), and as well many people who have little experience with LaTeX and need help with very basic things.


11

This is more of a comment to Martin Scharrer's answer (Case 2 of tohecz's answer), but too long for a comment... While I can't disagree with anything in Martin's answer (excluding the first part of the initial sentence), I personally would prefer that bugs be posted as a question here, even if they end up being closed. Many times it is not clear whether it ...


11

Sometimes it happens that the answer is a no-brainer, e.g. update the problematic package, forgotten ; at the end of a line in TikZ, etc. In such cases the answer is in fact a comment and it is hardly worth to bother converting it into a proper answer. IMHO these are candidates for deletion by the OP.


11

Just to stir up the soup. I agree with Alan Munn on this issue but with a slightly different motivation. I'm actually quite bothered by the word swiftly. I don't mind if the question stays open or closed, either way the issue is not resolved so no need to insist on practice because next year it would really be an ancient issue but as you can see it's ...


11

The reason such question are often closed it that bugs which will be fixed soon make the question "too localiced in time" because soon they issue will be gone and there is no suitable answer beyond "update the package". Note that our "no bug questions" policy is (or should be) IMHO mostly about questions which directly cover a bug, like "why do I get this ...


10

One of the advantages of the Stackexchange model is that there are ways to discuss and in fact reverse most decisions made by the community. It seems to me that if a case can be made on an individual question that it should be reopened, the threshold for reopening is not so high that it's very difficult to do. And we have the meta site for exactly this sort ...


9

Ironically, having just read through the answers and left a couple of comments, I headed over the main site and found Error message with hobby package which is essentially a bug report on the hobby package (which I maintain) and which has already been fixed. I would argue against closing this one because: The questioner doesn't know that it's a bug. ...


9

It is usually best to ask single, self-contained questions and include a minimal working example (MWE) that illustrates your problem. You could describe your end-goal in an attempt to guide answers. However, think of this site as a destination where not only you can find answers, but also others. Future visitors may not have the same end-goal as you, and ...


9

I just signed up for freelancer.ca (see edit below for more details) and basically you can look for freelancers in specific areas to do your "projects", including LaTeX. From what I can see, some of the freelancers seem to have really solid reviews and even have examples of their work. You can also post your "project" and have freelancers bid on it (but ...


8

As a novice-to-intermediate user, I might add that my knowledge of TeX plateaued for a long time before I found this site. I don't know anywhere else where I could get information of a quality comparable to, say, this answer: https://tex.stackexchange.com/a/83936/17049 Before I came here, I could get some kind of solution to many of the difficulties I hit ...


8

I'm not a lawyer, and copyright laws differ from country to country, but in the U.S., copyright does not need to be asserted: it exists the moment you produce the work. So in reality there is no such thing as "unknown copyright"; the safest assumption is that it belongs to the author or has been transferred to someone else. That said, it seems to me that ...


8

This is a little splitting the hair for my understanding. IF we force this I'm the first one who will stop using backticks :P We shouldn't have policies on such stuff because they are aids not rules. But at least we can embed some use into this pedantry if the backticked thing is a package name. We have the amazing tool of Martin Scharrer described here; ...


7

The benefits I see from a site like this is that it allows people to develop their understanding, regardless of prior knowledge, and by staying friendly, help spread TeX and make the community wider. I have seen horrible elitist behaviour on another site (not TeX related) where people quite angrily "yelled" at beginners for not having enough knowledge. It ...


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