-
Notifications
You must be signed in to change notification settings - Fork 41
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
discourse expressions with subjects #565
Comments
I think treating it as a |
I don't think you can simply omit "god forbid" here. In conversation maybe you could imply an "if" at the beginning of an utterance, but it looks off to do so in the middle of the sentence. Moving it to the end—"but they're not very communicative and something goes wrong god forbid, you'll have to fight to get it resolved."—looks as weird as simply dropping it. Yes the more basic function of "god forbid" is as an interjection-like discourse marker, so that holds if "if" is present.
Do you have a good example with a finite verb attaching as advcl? https://universal.grew.fr/?custom=67796187c8c36 is mostly turning up errors and constructions like "so X that Y". |
I'm pretty sure you can, you just need a nice phatic introducer to get the sentence started. How about "You know, something goes wrong, you'll have to fight to get it resolved"? It's similar to these real examples:
I could easily add "God forbid" to either of those:
It's maybe not the preferred variant, but you can find cases like that. It's easier if the protasis is short, but I think that makes sense based on general short-before-long preference. How about this?
It's also not hard to find real examples of post-posed God forbid, for example:
Sure, the one I quoted above is like that (it's from Reddit so wouldn't be included in your link): |
Those attestations fit what I meant by:
If somebody wrote "a little bit of frost God forbid, it's gone" I would simply be confused. If somebody spoke it with the right intonation, stressing FROST, it would make sense with "God forbid" as an optional discourse marker. I'm not arguing that "God forbid" is always or even usually a subordinator; I just have the sense that it licenses otherwise bare conditional clauses in environments where they would otherwise require another explicit marker like "if". But let's suppose this is too subtle to worry about for annotation. (After all, we treat words like "when" as |
Yeah, that sounds reasonable to me! |
…s with "forbid", "guess", "know", "mean", "think" (#565)
@amir-zeldes updated neaten.py. May be worth updating the GUM one for consistency. |
Added locally, will propagate for the next release |
The subject child rule in amir-zeldes/gum@efab974 flags "I guess", "I mean", and "God forbid" attaching as
discourse
. See UniversalDependencies/docs#1066 (comment). Should the rule be relaxed for these?In
it almost seems like "god forbid" takes the place of "if", so should it be a
fixed expressionfunctioning asmark
?? (UPDATE: actually maybe just the verb attaching asmark
instead ofdiscourse
, cf. "provided")The text was updated successfully, but these errors were encountered: