Skip to content

Add en-layperson language tag#1167

Open
haideriqbal wants to merge 1 commit intodevfrom
add-special-language-tag
Open

Add en-layperson language tag#1167
haideriqbal wants to merge 1 commit intodevfrom
add-special-language-tag

Conversation

@haideriqbal
Copy link
Copy Markdown
Collaborator

@matentzn here you go!

Copy link
Copy Markdown
Contributor

@matentzn matentzn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great, thanks - but wait before merging; I need to confirm this is the exact TAG we want to use here with the rest of the community

@cthoyt
Copy link
Copy Markdown
Contributor

cthoyt commented Feb 10, 2026

I would prefer this were solved using OMO synonym types (i.e., OMO:0003003 for layperson synonym) rather than misusing language tags

@matentzn
Copy link
Copy Markdown
Contributor

I would prefer this were solved using OMO synonym types (i.e., OMO:0003003 for layperson synonym) rather than misusing language tags

Me too. @haideriqbal would you see it anywhere in the realms of the doable to build a "synonym type switcher" widget just like the language widget instead of this "hacky" suggestion here of overloading the language tag switcher? It IS a compromise, what @cthoyt is saying is much cleaner and we dont need to maintain this feature moving forward.

@jamesamcl
Copy link
Copy Markdown
Member

My current opinion is that the language tags are a reasonable practical way to store this information and I think another dropdown would be confusing for users. Happy to change my mind but I don’t think it is clear cut right now.

Wikipedia considers “simple english” to be a language for example https://simple.wikipedia.org/wiki/Main_Page they don’t have English Wikipedia overloaded with an extra dropdown for how complex you want the words

@jamesamcl
Copy link
Copy Markdown
Member

Having said that, regardless of how the layperson synonyms are stored I think unlike alternate languages they should always be visible on the page with the other synonyms.

@matentzn
Copy link
Copy Markdown
Contributor

I mean, another dropdown is not necessary - it could be a single drop down but powered by two different systems: language tags and synonym types. You could visually separate them a little in the switcher and would be fine.

@cthoyt is I assume not just looking at "layperson", but also UK spelling, International Nonproprietary Name, "legal name" and any other such types.

Having said that, regardless of how the layperson synonyms are stored I think unlike alternate languages they should always be visible on the page with the other synonyms.

Agreed - they are, but not the synonym type is currently folded into the little (i) info button next to the synonym.

@haideriqbal
Copy link
Copy Markdown
Collaborator Author

@matentzn what have we decided on this one exactly?

@matentzn
Copy link
Copy Markdown
Contributor

Can we park this as a draft? I did not get the responses I need yet..

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

Successfully merging this pull request may close these issues.

4 participants