Update: This was almost certainly my fault.
On December 20, 2013 I moved the TeX (and meta) databases to new homes. I'm not sure how the original problem occurred, but TeX and its meta had a very odd database collation. Of the hundreds of databases, it was only those. We didn't recognize this for several years until we started aggregating data across ...
Reading some feedback on meta.stackexchange.com I got the impression that this community feels quite tense about the upcoming CommonMark migration. I feel that some extra levels of transparency shared right here might make your lives a little easier and help alleviate some of the tension, so let me try to address some of the concerns and give you a more ...
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 ...
Based on \\ corruption, I've created a new query
TeX.SX \\ corruption (based on user ID)
which I hope will help anyone to find their own posts affected by this bug!
P.S. The database is updated every sunday, so the query will return also updated Q&A until the database is refreshed...
For users who are curious about how the automated edits look like, and who want to review them for potential issues: visit the profile of the Community user (ID -1), and navigate to 'all actions' → 'revisions', or use this direct link.
They'll be recognizable by the edit summary "Commonmark migration":
(screenshot taken from Meta.SE pending the actual ...
Issues using a variety of software - Pandoc included - are on topic here as long as the issue relates to (La)TeX in some way. As mentioned in the TeX - LaTeX Tour page:
Formats like LaTeX, ConTeXt and plain TeX
Engines like pdfTeX, LuaTeX and XeTeX
Distributions like TeX Live, MiKTeX, and MacTeX
Related software and tools, BibTeX, MakeIndex, ...
I believe there's an answer on MSE that addresses the issue. The important bit is:
A colon and %3a are semantically identical in URLs per the RFC.
If you look at an example on Gaming (and read the comments), you'll see that the problem should actually be fixed by the site that serves pages with colons in the URL. This is actually a bug at Gitorious.org. ...
This all has to do with the fact that SE uses markdown in posts and comments (similar to setting some character's catcode to \active), and markdown uses the following set of characters that have special meaning:
[, ] Used with links/internal references/tags
(, ) Used with links/internal references
! Images, language syntax formatting and spoilers
First of all, the help page on editing mentions no guidelines in terms of such edits. Furthermore, policy is too authoritative here, and technically it would not be enforceable. One could suggest some guidelines, but then again, not everyone will follow them (see oNe SuCH iNSTaNCe).
This is not very different from people putting "Thanks" at the bottom of ...
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; ...
As you can see on the revision page which shows a live rendering of this question, this is fixed now. It's still visible in your question because the version displayed here is saved on submission; were you to edit the question now, the stray </li> would be gone from there as well.
If you're interested in some technical background on the problem, I ...
Does the package name have to be typed exactly so in the preamble or you get an error? It won't work if you use a synonym, different capitalization, or hyphenate? Why then, it really IS code after all, just a very small excerpt.
This issue has been raised several times, and the central concern remains the same. When people need to show what they are seeing from TeX, we all need to see exactly what they see. Using some installed TeX system would run the risk of different package versions, etc., which might impact on the situation.
More broadly, it's only in a minority of cases that ...
I do not know a site solution, but you can try to solve his on your own:
For Windows there is PhraseExpress, a text expander for Windows (free for personal use), and I guess there are alternatives for Linux and MacOSX, for Windows I know there are. I use this myself for instance to get typographical quotes like “” and ‘’ (also in German „“ or with ...
This and the linked question
‘double backslash + newline’ collapses to ‘single backslash’ when I hit ‘edit’
Are two manifestations of the same issue, see
Community effort in fixing the double backslashes issue
For a summary of how this got fixed in the end.
The markdown backtick syntax does not only the formatting like the HTML <code> block, but it also escapes special characters, so a \ or a < or > have no special meaning. Inside a <code> block this escaping does not happen, so a backslash introduces an escape sequence. To have a backslash you need an escaped backslash, thus: <code>\\@...
Indeed. This seems like a markdown "typo." However, it is a network-wide issue and should therefore be addressed at that level. There is a similar question related to this posted on the main network meta: Markdown help page is broken (badly presented/formatted) on every site.
I've looked into it and I couldn't find anything specific. The thing is, we don't ever modify markdown w/o recording history. So when you read about rebakes and other stuff we do, those are affecting the conversion from markdown to html, with markdown always staying the same.
To me, this looks like a one off job that somebody ran on the DB that touched post ...
Testing link prettification for https URLs:
Testing link prettification for http URLs:
Testing link prettification for protocol-less URLs: