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

How to deal with intended translations for ungrammatical forms? #25

Open
jrwdunham opened this issue Dec 12, 2014 · 0 comments
Open

How to deal with intended translations for ungrammatical forms? #25

jrwdunham opened this issue Dec 12, 2014 · 0 comments

Comments

@jrwdunham
Copy link
Owner

I've just followed the convention of putting "Intended: ..." into these types of translations(/glosses). (Alternatively, one could just put the intended translation without the prefix "Intended: " since that seems implicit, given that the form is marked as ungrammatical.) Are there any issues with just using the "Intended: " prefix as a convention? Should there be a separate field for this? If so, should it be separate from the "translation appropriateness" field?

The OLD doesn't use the translation information in any of its logic so "Intended: " in a translation string shouldn't mess anything up.

Another option would be that if a form is ungrammatical the system could just automatically display any translations with an "Intended: " prefix.

Can we think of scenarios where an ungrammatical form would have a translation and where calling that translation "intended" would be inaccurate?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant