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

Help wanted: Difficulties with making scandinavian special characters in language patch. #354

Closed
larswd opened this issue Nov 12, 2023 · 1 comment

Comments

@larswd
Copy link

larswd commented Nov 12, 2023

I am working on an adventure for my play group, and made a language patch to Norwegian. Unfortunately, I encountered some difficulties with the lodalization process.

One problem is with the special charaters æ and å. Specifically, these are not recognised by the latex compiler in the language.sty file (but still works as intended in the main document. Looking around at the world wide web, I found out that \aa should be the command for å and \ae for æ. The former of these two yields me an å, but it does "swallow" any following spaces meaning I have to use the slightly incorrect translation "for treff" for "to hit", rather than "for å treffe". The letter æ is, however, more problematic as the suggested command \ae does not work. By writing æ directly into the sty-file, I get:

bilde

and with \ae I get:

bilde

Clearly, neither is a specially good representation of æ. Are there any known way of getting around this problem? I am compiling with pdf-latex and using the norwegian babel package with the utf8 inputenc as my language package.

PS: There also seems to be the problem that the package adds a space between the word for damage "skade" and the damage type, as can be seen above with "stikk skade", which is a grammatical error. For some damage types, like necrotic (nekrotisk) it works as you can make the damage type into an adjective, but for piercing, slashing and bludgeoning I am not sure if there are any good workarounds for this. ANyone know how to concatonate these?

@larswd
Copy link
Author

larswd commented Nov 14, 2023

I tried around with compiler tricks motivated by #346 and switching compiler to XeLaTeX did the trick

@larswd larswd closed this as completed Nov 14, 2023
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

1 participant