You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: