Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
For example, in this help page about finding and replacing with gsub() in awk:
I know now that the [ ] used in [, t] means that t is an optional argument, but I only know this now because my colleague told me. He did not know where he learnt this, my guess is that there are some commonly used conventions that help pages follow but I lack the vocabulary to be able to search for such conventions.
What other common formatting conventions are used when it comes to help pages? Where can I find out about them?
What you are looking for is called Command description syntax on Wikipedia or Utility argument syntax in The Open Group Base Specifications.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
The javadocs at http://www.frege-lang.org/doc/index.html seem to be missing quite a bit (namely, no frege.prelude package), and does not seem very up to date. Might there be a good documentation for Frege hidden in plain sight somewhere?
What you have seen is the API doc of the runtime classes, which is really minimal since the typical Frege user will not work with those.
Thomas correctly pointed to the library documentation.
In addition, there is "Hoogle" support for Frege: http://hoogle.haskell.org:8081/ where you can search the API.
All is linked from the Frege home page.
Hope that helps.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I wanted to know the spell correct api's available for commercial/non commercial usage other than google/bing.
First of all you can write your own spell corrector with this tutorial. In addition there are some Python packages that may help you with that, such as TextBlob (which I highly recommend). Another option is Gingerit which Iv'e never tried but looks promising. Another DIY spell correct tutorial might interest you as well.
https://www.gigablast.com/spellcheckapi.html
I just launched this, so it's still beta, but it's not bad. It has a dictionary of over 600,000,000 entries covering most non-Asian languages.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Is there a cheatsheet that compares the usage of Markdown with Restructure? With this, I could learn rst faster if I already knew Markdown. I tried google for it but haven't found one..
A small comparsion from a lot lightweight markup language syntaxs can be found on Wikipedia.
There is also a Gist document about the common markup between the two languages.
You can use Pandoc to convert your existing Markdown to reST or the other way around.
There are a lot of different Markdown dialects, so it may be difficult to compare the syntax with reST.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I'm trying to understand how documentation generators like Doxygen, JavaDocs etc. work. Please don't get me wrong, I'm not asking how to use them, but how they do it. I tried to find information about the topic but only found 1 article which is really old, so I'm kinda frustrated.
Does someone know any articles or literature about this?
For doxygen there is a manual page about the internals of Doxygen.
Some small document generators just use regular expressions to extract the documentation. The more flexible and complicated way is to develop a parser for the language and a parser for the documentation syntax just like doxygen and Javadoc do.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Does anyone know of a newer standard for software interface specifications than IEEE J-STD 16 1995? I have been searching the web and the IEEE site and have not found anything, but may not be using the right combination of words in my searches.
I believe the standard that replaced J-STD-016-1995 was IEEE 12207.
The standards that defined the Software Life Cycle Process evolved in the following order:
MIL-STD-2167 (1988) & MIL-STD-7935A (1988)
MIL-STD-498 (1994)
J-STD-016-1995 (1995)
IEEE/EIA 12207 (1998)
Source
From all of the information that I have been able to gather, this is the best standard. There are others out there or I could create my own format, but this one seems to be the most accepted....for anyone who wishes to know an answer to this question.