| Age | Commit message (Collapse) | Author |
|
This turns error messages like
gf: too few bytes. Failed reading at byte position 1
gf: /some/path/somefile.gfo: too few bytes. Failed reading at byte position 1
but a better fix would be to ignore bad .gfo files and compile from source.
The problem is the way this decision is made in
GF.Compile.ReadFiles.selectFormat...
|
|
Also added feedback to source & target language menus to indicate which
languages are supported by the selected translation method. For Apertium, the
source language menu shows all possible source languages, and the target menu
shows the possible target languages for the chosen source language.
|
|
up the code a lot
|
|
some other small fixes
|
|
|
|
This prevents from explosion in the memory size but it will also prevent us from parsing some sentences.
|
|
fair basis with the grammar rules
|
|
|
|
Also some small cloud service documentation updates.
|
|
|
|
|
|
|
|
|
|
The Setup.hs script now queries darcs to create more detailed version info
to include in the startup message.
Note thought that with distributed version control systems like darcs,
the only way to uniquely identify a version is by the set of patches included.
Since the patches are not totally ordered, just looking at the last patch is
not enough.
For official releases, we tag the current set of patches so we can refer to
it by name (e.g. RELEASE-3.3.3).
|
|
|
|
The translator picks "the first" translation by default, but the user can
choose among the generated translations from a popup menu.
|
|
This fixes a bug introduced on May 16.
|
|
This is in addition to the existing "Segment by Segment" view.
Also some minor documentation updates.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
warning if it is missing
|
|
|
|
|
|
|
|
Note though that the unlexer does the wrong thing with initial words that are
supposed to be capitalized, e.g. "I am ready.", "Spanish wine is good.", so
these sentenses are not translated at the moment.
|
|
|
|
|
|
|
|
My menu hiding hack didn't work in Gecko browsers because of a difference in
the behaviour of the JavaScript setTimeout function.
|
|
It is part of the cloud services available with gf -server.
|
|
* Update Setup.hs to build Japanese by default.
* News item about Japanese on the home page.
* Add Japanese to the supported RGL imports in the grammar editor (gfse).
|
|
|
|
your own risk.
|
|
|
|
|
|
As a temporary workaround, alex is no longer invoked automatically when
building with cabal. Developers who want to modify the lexer need to run
alex on Lexer.x manually and record the modified Lexer.hs.
src/compiler/GF/Grammar/lexer/Lexer.x -- hidden from cabal
src/compiler/GF/Grammar/Lexer.hs -- update it manually
|
|
|
|
with pgf_online.js
This makes the minibar offline demo work again.
|
|
words when possible
Instead of showing the name of a function in the abstract syntax, linearize it
and show the result. For functions with argument, e.g. That : Kind -> Item,
the function is applied to the right number of placeholder arguments: 'That ?'.
If the linearization fails, the name of the function is shown anyway.
|
|
The grammar extension is now done with a regular HTML form, so you can use the
TAB key to move between the fields and press ENTER to submit the extension when
you are done.
TODO: more immediate error feedback
|
|
Also include the GF logo on the cloud service start page.
|
|
Document recent additions in minibar/about.html.
|
|
This functionality was available in the origial Fridge Poetry app, but has been
missing in minibar until now.
|
|
word-for-word replacment on or off
|
|
The current intput is now represented as an array of words instead of as a
string.
(This is the kind of change is scary to do in a dynamically type language
like JavaScript. In a statically typed language like Haskell you can do it
with confidence, since you know the compiler can help you catch all mistakes...)
|
|
Get rid of list of previous states, which was only used to delete the last
word.
|