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

Added translation nb.yaml #9095

Closed
wants to merge 4 commits into from
Closed

Added translation nb.yaml #9095

wants to merge 4 commits into from

Conversation

sda030
Copy link
Contributor

@sda030 sda030 commented Sep 22, 2023

Added nb.yaml, which is a duplicate of no.yaml.
no=Norwegian major language consists in reality of two microlanguages nn=Nynorsk and nb=Bokmål. Downstream software (Quarto) requires consistency.

Norwegian consists of two official languages Nynorsk (nn.yaml) and Bokmål (nb.yaml). The current file no.yaml refers to the macrolanguage and an informal understanding of Bokmål as reflecting the macrolanguage. However, some downstream pakcages (Quarto) requires nb.yaml to exist. See also 3.1.10. at https://www.rfc-editor.org/rfc/rfc5646.html or look up Norwegian at https://r12a.github.io/app-subtags/
@jgm
Copy link
Owner

jgm commented Sep 22, 2023

Thanks. I'd prefer no unrelated changes (e.g. .gitignore) in the PR.

Also -- would it be better to make nb.yaml a symlink to no.yaml (or the reverse), rather than duplicating contents?

@sda030
Copy link
Contributor Author

sda030 commented Sep 23, 2023

Ah, sorry about .gitignore. Also, I did not know/think about the symlink possibility. Is hard or soft link preferred? Let me try once more please, I am a bit new to PRs and pandoc dev.
EDIT: I think no.yaml (as the major language) being the symlink (as it is technically a shorthand for nb.yaml) is more appropriate linguistically speaking.

@sda030 sda030 closed this Sep 23, 2023
@sda030 sda030 deleted the add_translation_nb branch September 23, 2023 12:26
@jgm
Copy link
Owner

jgm commented Sep 24, 2023

I think that making it a symlink is the best approach. I think git handles that fine as long as it's a relative link to a file in the same repository.

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.

2 participants