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

have 2nd set pronouns be 2nd part of 1st pronouns in api if secondary pronouns are not set #132

Open
valiray opened this issue Jan 11, 2025 · 1 comment

Comments

@valiray
Copy link

valiray commented Jan 11, 2025

i was messing around with the api for something i am using and found that it only responds with "she" when i have my pronouns set to she her and i hoping this could be changed or at least was wondering if i could be told why it was did in this way

@cyyynthia
Copy link
Owner

The API does not serve as a presentation layer, and only carries over the wire the raw data specified by users. It wouldn't make sense in terms of data structure to carry "her" over the wire if a user only specified the she/her set; 1 set selected, 1 entry in the sets array.

The presentation is left to the API consumers to figure out, as there is not a unique and/or universally agreed upon standard for displaying this information, internationally and in multiple-sets cases.

  • In France, it is somewhat common to only mention the subject form (e.g. elle) without the object form (e.g. elle/la).
  • For multiple sets, one may opt to use she/it, or she/her/it/its, or she/her or it/its, although the compact form is more common than the expanded forms (and there are other forms people may chose to use.
  • Depending on the use case, especially in space-constrained places, it may be relevant to only show the subject form and/or limit the amount of sets displayed. For example, the extension only shows up to 2 sets in Twitch chats.

It can also be relevant to let the user choose how they want to see pronouns; the extension currently lets people configure the casing (she/her vs She/Her), and more configuration may be added sometime:tm: in the future. A good example would be subject+object form vs subject-only form, for French speaking users.

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

2 participants