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

Multiple translations of 'et al.' #123

Closed
5ke opened this issue Nov 10, 2015 · 3 comments
Closed

Multiple translations of 'et al.' #123

5ke opened this issue Nov 10, 2015 · 3 comments

Comments

@5ke
Copy link

5ke commented Nov 10, 2015

Hi,
This issue is somewhat related to issue #6. There seems to be some disagreement whether one should translate 'et al.' to 'mfl.', 'm.fl.' or just simply 'et al.' in Norwegian.
I'm not going to argue about which one is right, because I expect different fields have different habits anyways.

Is there any way by which multiple 'et al.' translations can be added to the locale sheet in such a way that the user of a specific style gets to pick the one that suits him/her best?

@adam3smith
Copy link
Member

Beyond the et al./and others distinction there is no way to add multiple translations of the same term to a style, no. The situation you describe is not at all uncommon: even in English, for example, we see different abbreviations for edition (ed. and edn.), German has the same issue with using both et al. and its German translation, etc.

The place to adjust this is the citation style itself. You can override global term definitions in citation styles using (e.g.)

<locale xml:lang="nn-NO">
  <terms>
    <term name="et-al">et al.</term>
  </terms>
</locale>

to change mfl. to et al. Letting style users pick individual terms is certainly not something we'd want to do in CSL. If there's high demand, reference managers could certainly implement some version of this (where they offer you to override existing terms), but given how long it has taken them to even implement proper locale support, I very much doubt that's something they're interested in.

@5ke
Copy link
Author

5ke commented Nov 11, 2015

Ok, I was afraid that it would be like that. To be honest, I was rather pleasantly surprised there was support for Norwegian at all. Thank you for your reply :-)

@rmzelle
Copy link
Member

rmzelle commented Nov 23, 2015

(so currently, we always try to use the most common translation of each term in the locale files, while allowing individual styles to define overriding translations.)

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