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

Gender specification in sketches #15

Open
kunal-mohta opened this issue Feb 19, 2018 · 8 comments
Open

Gender specification in sketches #15

kunal-mohta opened this issue Feb 19, 2018 · 8 comments

Comments

@kunal-mohta
Copy link
Contributor

Right now if the user wants to include a gender specific word like his/her, he/she, etc., then it needs to be hard coded. What it means that the user will have know before hand what the gender is.
Maybe you could add a way to let user specify the statement to be used for a particular gender.

It could be done in the following way -

root:
- (male) {{ giver }} did his job.
- (female) {{giver}} did her job.

This is just a suggestive syntax. It should obviously be decided by you.

@fdb
Copy link
Member

fdb commented Feb 19, 2018

To generalize this problem, we could introduce a system of dictionary lookups that can match keys to values. In the gender case, it could match names to pronouns, for example.

JavaScript uses the {key: value} syntax for this, which I like. I'm not sure where we would put these dictionaries, though.

@kunal-mohta
Copy link
Contributor Author

I don't quite understand what you are suggesting.
Can you please elaborate.

@TanviKumar
Copy link
Contributor

TanviKumar commented Feb 19, 2018 via email

@kunal-mohta
Copy link
Contributor Author

Can you give an example of the key:value structure.

@TanviKumar
Copy link
Contributor

TanviKumar commented Feb 19, 2018 via email

@kunal-mohta
Copy link
Contributor Author

I think @fdb mentioned that the names should be matched to the pronouns, which means it should be like Tarun : his, I guess.
As of the question about where should these be I guess the following way suits -

giver:
- Tarun { gender : male }

We can then have our own dictionary specified like -

male => {
    pronoun : he,
    determiner : his
    ....
}

And then user can directly use {{ giver.pronoun }}, where if in the random seed Tarun is chosen, then we already know that we have to use the grammar for male.

@fdb
Copy link
Member

fdb commented Feb 20, 2018

I'm not quite sure how it would work. I think we need to look at it more generally, not just as a gender-specifier but as a generic mapping from keys to values. I'm open to suggestions for how the syntax might look...

@kunal-mohta
Copy link
Contributor Author

I think what I suggested earlier can help the user to write of the generic cases.
However, as the developers of the language, you could only provide the user with the syntax, how they are able to use that to achieve what they want, largely depends on how they implement it.
There are huge number of cases related to this, like how verbs can take different forms if the options have both singular and plural objects. But I think these would be a task for the user to decide on how to use the existing syntax to achieve the required result.

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

No branches or pull requests

3 participants