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

Swedish - grammar and spelling corrections #150

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Liggliluff
Copy link

Numeral names in Swedish is written together as one word, except for names above "miljon" (million) and if the number is 21-999 (except ending in 0) preceding "tusen" (thousand). Also for 1, "ett" is often used; when preceding "hundra" (hundred) and "tusen" (thousand), "ett" is always used. Before "miljon" (million) and larger names, "en" is used instead. – So "21" and "100" would be "tjugoett" and "etthundra" instead of "tjugo-ett" and "en hundra".

Numeral names in Swedish is written together as one word, except for names above "miljon" (million) and if the number is 21-999 (except ending in 0) preceding "tusen" (thousand). Also for 1, "ett" is often used; when preceding "hundra" (hundred) and "tusen" (thousand), "ett" is always used. Before "miljon" (million) and larger names, "en" is used instead.
@coveralls
Copy link

coveralls commented Nov 29, 2017

Coverage Status

Coverage remained the same at 99.291% when pulling ac4df8f on Liggliluff:patch-1 into 5998291 on kslazarev:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.291% when pulling ac4df8f on Liggliluff:patch-1 into 5998291 on kslazarev:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.291% when pulling ac4df8f on Liggliluff:patch-1 into 5998291 on kslazarev:master.

@dblock
Copy link
Collaborator

dblock commented Jul 23, 2022

I know this is old but maybe @Liggliluff would be interested in finishing this?

@Liggliluff
Copy link
Author

@dblock I started on this, got an error, and I have no clue how to resolve it, and gave up. If someone else wants to fix this error, go ahead. Alternatively creating a new pull request with the same changes without the error.

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.

3 participants