Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: different backup options #22

Closed
inariksit opened this issue Jan 26, 2022 · 0 comments · Fixed by #25
Closed

Feature request: different backup options #22

inariksit opened this issue Jan 26, 2022 · 0 comments · Fixed by #25
Labels
enhancement New feature or request

Comments

@inariksit
Copy link
Member

Two things: Backup cat + funs, and string literal funs.

Backup* funs

In the current master branch, Backup* funs are added by default, if some parts of the sentence can't be included in the GF tree. However, this requires that the grammar contains such funs, which not all grammars do. So I would like to have this feature optional.

It can either be a command line argument, or the Haskell code can check whether the PGF contains a cat called Backup and funs called BackupNP etc., and use them only if they are found in the PGF.

I don't care about which way to use, just to have the feature optional in some way.

String literals for OOV words

If the sentence contains words that are not in the lexicon, I would like to create those words as string literals. So "mimsy were the borogroves" would result in an otherwise normal GF tree, but with the subtrees StrA "mimsy" and StrN "borogrove".

Again, this feature should be optional: either command line arg, or check if the grammar contains StrA : String -> A.

Future work: modify the PGF grammar?

The new majestic runtime will allow modifying PGFs on the fly. So when that is possible, I'd prefer to create proper lexicon entries mimsy_A and borogrove_N, using real GF smart paradigms, and insert them into the PGF. Similarly, the Backup* funs would also be possible to insert into the PGF.

So once the new runtime is in place, I think that command line argument would be a better option. And if these features are added into gf-ud already before majestic runtime, it makes sense to just use command line arguments from the beginning. (I don't care which option is the default.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant