| Age | Commit message (Collapse) | Author |
|---|
|
it still produces the right TTS
|
|
|
|
database
|
|
|
|
|
|
|
|
|
|
By adding unlexer=none (or unlexer=id) in requests that output linearizations
(e.g. command=linearize, command=translate), you can leave &+ uninterpreted
instead of gluing the adjacent tokens. This means that the output is left in
a format that can be parsed in a subsequent request.
To implement this consistently, the function linearizeAndBind was replaced
with the function linearizedAndUnlex (but there are a couple of requests
that do not call this function...)
Note that this applies to the Haskell run-time requests only. The C run-time
request (c-linearize, c-translate) always applies the &+ token and the
c-parse request can parse input containing glued tokens.
|
|
|
|
|
|
lightning
|
|
shown with Chinese characters
|
|
|
|
|
|
This means more compact JIT compiled code and uniformity with the code for def rules
|
|
|
|
|
|
|
|
version
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Becacuse of the new special tokens added to the Symbol type, .gfo and .pgf
files produced with the current version of GF can not always be used with
older versions of GF and the PGF run-time system.
The PGF version number was increased from (2,0) to (2,1). GF can still
read version (2,0) and (1,0), so old PGF files continue to work.
The GFO version was increased from "GF03" to "GF04".
|
|
|
|
entry. Now this is fixed by treating those as syntactic rules
|
|
|
|
|
|
|
|
but much faster
|
|
Also fixed a problem with showing inflections for words containing underscores
(e.g. race_2_N).
|
|
minibar_support.js
|
|
Minibar needs js/langcode.js now, so need to include it in gfse/index.html
and syntax-exitor/editor.html too.
|
|
|
|
|
|
|
|
NERC in Haskell and Java now refuses to recognize names that match words in the lexicon. The latest is useful for German
|
|
|
|
supported by the browser
|
|
|
|
|
|
if case_sensitive=off
|
|
|
|
|
