We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes the pluralize js lib gets it wrong. There is an API to fix a word, and we should PR them instead, but for lazy one offs... let's do it?
= Mitochondrion {p=Mitochondria} \x[mitochondrion]{p}
or perhaps with a separate header:
= Mitochondrion = Mitochondria {synonym=plural}
?
A workaround for this especially when {p} does not cut it because the plural is not the last word is to use {synonym}:
{p}
{synonym}
= Shade of grey = Shades of grey {synonym}
maybe that is good enough actually.
The advantage of {p} is that is does not take up extra ID space. The diametrically opposite proposal is done at: #165
The text was updated successfully, but these errors were encountered:
E.g. pluralize bugs: plurals/pluralize#172
Sorry, something went wrong.
No branches or pull requests
Sometimes the pluralize js lib gets it wrong. There is an API to fix a word, and we should PR them instead, but for lazy one offs... let's do it?
or perhaps with a separate header:
?
A workaround for this especially when
{p}
does not cut it because the plural is not the last word is to use{synonym}
:maybe that is good enough actually.
The advantage of
{p}
is that is does not take up extra ID space. The diametrically opposite proposal is done at: #165The text was updated successfully, but these errors were encountered: