| Age | Commit message (Collapse) | Author |
|---|
|
functions now return both the generated tree and its linearization
|
|
in the types
|
|
in the abstract syntax
|
|
|
|
When pfg-server servers a static file in HTTP mode, it is output as is, so
specifying charset="iso-8859-1" could be wrong.
Note: the a charset can be specified with a meta tag in HTML files,
e.g. for files in UTF-8:
<meta http-equiv="Content-type" content="text/html;charset=UTF-8">
|
|
It is needed for the userLanguage field in the grammar info from pgf-server
|
|
prevented the fridge and translate web apps from working
queryToArguments "?&input=bla+bla"
returns [("&input","bla+bla")]
but should return [("input","bla bla")]
|
|
refers to a directory
|
|
HTTP mode
|
|
pgf-server can now act as a standalone HTTP server. To activate this mode,
start it with
pfg-server http
to use the default port number (41296), or give an explicit port number, e.g.,
pgf-server http 8080
The HTTP server serves PGF files in the same way as the old FastCGI interface.
In addition, it also serves static files. The document root for static files
is the www subdirectory of the current directory where pgf-server is started.
In spite of these addition, backwards compatibility is maintaned. The old
FastCGI interface continues to work as before. (It is activated when
pgf-server is started without arguments.)
|
|
parse forest
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
show all alternative disambiguations for each alternative translation
|
|
functionality is exposed by parse_
|
|
|
|
|
|
binary for the output
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
from deprecated
|
|
|
|
|
|
well as list of categories
|
|
|
|
|
|
|
|
|
|
|
|
|
