Pronoun-related updates to people page

Two requested changes:

1. Add optional pronoun.is urls to people's contents.lr files and display them as clickable link. Pronoun island urls are non-trivial, so it would most likely be best to store the pronoun.is url and the existing pronoun string as separate things (rather than attempting to create a mapping).

2. Change PRO: string in people.html to appropriately styled 'pronoun:' string.

Trac:
Parent Ticket: #29901 (moved)

added component::webpages/website owner::hiro parent::29901 priority::medium resolution::fixed severity::normal status::closed type::defect labels

Trac:
Description: pronoun.is urls are non-trivial, so it would most likely be best to store the pronoun.is url and the existing pronoun string as separate things (rather than attempting to create a mapping).

to

Two requested changes:

1. Add optional pronoun.is urls to people's contents.lr files and display them as clickable link. Pronoun island urls are non-trivial, so it would most likely be best to store the pronoun.is url and the existing pronoun string as separate things (rather than attempting to create a mapping).

2. Change PRO: string in people.html to appropriately styled 'pronoun:' string.
   Summary: Add support for pronoun.is to people page to Pronoun-related updates to people page

Several approaches I can think of:

1. "pronoun: they" as link text for a link to a pronoun.is URL
2. "pronoun.is/they" as link text for a link to a pronoun.is URL

One drawback to (2) is it might be harder to localize, but localizing pronouns is very tricky anyway. On the other hand, with (2), we can store the pronoun.is URL directly, and display only that.

For better-known pronouns, pronoun.is URLs are fairly regular (even ones that provide alternatives, like pronoun.is/they?or=she or pronoun.is/they/:or/she, though those might have too much punctuation to display as the link text).

Trac:
Cc: traumschule to traumschule, catalyst

Hi we do not have a complex mapping of pronouns. For us a pronoun is a string not an array... so having that mapping might be super complicated. What we can do is that if people want they can use the pronoun.is api and provide a link to a PR for their people contents.lr. Then in lektor I will build a macro that verify that the pronoun field is a link or not. if it is displays the link provided otherwise just the text. Is that ok? -hiro

Of course super complicated might be an exageration as we can have a reg ex reading the field and makeing the necessary assumption, but I'd prefer not to over engineer this. Another possibility is that people use in the test they provide the url part of what they want pronoun.is to point to... that could actually be more straight forward...

Using pronoun link directly in the field. I think this is an ok approach.

Trac:
Status: assigned to closed
Resolution: N/A to fixed

closed

mentioned in issue #29901 (moved)

moved to tpo/web/trac#29910 (closed)