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

Add Latin translation #589

Open
quaepoena opened this issue Jan 2, 2023 · 3 comments
Open

Add Latin translation #589

quaepoena opened this issue Jan 2, 2023 · 3 comments
Labels
translation Translating the deck to a new language

Comments

@quaepoena
Copy link

Hello,

I'd like to translate the deck into Latin and will soon begin doing so. Beyond following the guidelines in CONTRIBUTING.md is there anything else I should keep in mind?

Thanks.

@aplaice
Copy link
Collaborator

aplaice commented Jan 2, 2023

Thanks very much!

The only things that come to mind, that might be relevant, are:

  1. choice of orthography.

    To the very limited extent that I have an opinion, I would be mildly in favour of having the u/v split, but a single i. That seems to be what Latin Wikipedia have standardised on.

  2. choice of vocabulary for the longer fields (capital/country info, flag similarity etc.) — i.e. Classical Latin vs. Ecclesiastical Latin vs. everything in between vs. not settling on anything in particular.

    AFAIK the difference is very slight, so it might not matter; given the brief sentences we have, all of these might be more-or-less identical.

Unless axelboc or ohare93 know Latin better than me, we're not really qualified to judge, so you'll need to make these decisions yourself (i.e. please feel free to decide whatever feels most sensible or most convenient for you) and ideally please record them for future reference (in CONTRIBUTING.md, like for Norwegian and Portuguese), at the end.

@axelboc axelboc added the translation Translating the deck to a new language label Jan 2, 2023
@quaepoena
Copy link
Author

Noted and agreed on "u/v" and "i," and I'll be using Classical Latin. When there are several options for a given name, I use the name of the article in Latin Wikipedia, though I (currently) have two guidelines on whether to include another name in capital_info.csv

  1. If the names are very similar, e.g. with Budapestinum vs Budapestum, I don't mention the alternate form.
  2. If there's a phonlogically unrelated name that seems interesting, as with Nuuk/Bona Spes, I include it.

The second guideline is subject to change if I find that capital_info.csv has become too cluttered.

Lastly, I had initially thought to include macrons due to personal preference, though, seeing that Latin Wikipedia has standardized on not using them, I'll forego that. Another reason to not use them here is that most of the reference works for these place names don't use them, and, therefore, I could never be certain if a given name has a long or short vowel in a given position. I could make an educated guess, of course, but I think consistency, coupled with adherence to the widely accepted orthographic standard, is better.

@quaepoena
Copy link
Author

Hello,

I just wanted to say that I'm still chipping away at this, slowly but surely. I'm currently working on translating the last of the .csv files, and then I'll go back through and double-check everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
translation Translating the deck to a new language
Development

No branches or pull requests

3 participants