| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
GF cat, instead of the old Concrete syntax name + index among all CFG cats.
|
|
ENBF printing patch.
|
|
each GF category, instead of being the FCFG category number.
|
|
|
|
constituent.
|
|
|
|
|
|
|
|
|
|
GF.Speech.PGFToCFG, but should probably move somewhere else.
|
|
|
|
|
|
|
|
|
|
|
|
value of GF_LIB_PATH
|
|
|
|
|
|
|
|
|
|
server,
|
|
Accept-Language header.
|
|
|
|
|
|
best matches the Accept-language header.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
hardcoded paths in the compilation).
|
|
|
|
only on what appears to be string literals.
|
|
The problem is that lower case a with a grave accent is coded in UTF-8 as \195\160.
Unicode character \160 is non-breaking space, so Haskell's words function
will break a UTF-8 encoded string at this character.
String literals in the .gfo file are UTF-8 encoded in generateModuleCode,
just before the call to prGrammar (which uses compactPrint, which used words).
The real solution would be to pretty-print the grammar to Unicode, and then
encode as UTF-8. The problem with that is Latin-1 identifers. They are now
kept in Latin-1 in the .gfo file, since Alex can't handle Unicode.
The real solution to that would be to fix Alex to handle Unicode, but
that is non-trivial. GHC interally uses a very hacky .x file to be
able to lex UTF-8 source files.
An alternative solution that doesn't address the weirdness of using two different
encodings in the same .gfo as we do now, is to incorporate compactPrint
into the grammar printer, to avoid having to do any postprocessing.
|
|
|
|
|
|
|
|
|
