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

Use "Mg" instead of "$" sign #6

Open
Wuzzy2 opened this issue May 27, 2021 · 5 comments
Open

Use "Mg" instead of "$" sign #6

Wuzzy2 opened this issue May 27, 2021 · 5 comments

Comments

@Wuzzy2
Copy link

Wuzzy2 commented May 27, 2021

The mod uses the dollar sign "$" to abbreviate the currency but it should be "Mg" (for "Minegeld"). "Mg" is how the currency mod abbreviates "Minegeld".

@Git-Forked

@Wuzzy2
Copy link
Author

Wuzzy2 commented May 27, 2021

Oh, and the "Mg" is also written after the number, not before.

For example: Instead of "$5", write "5 Mg".

@h-v-smacker
Copy link
Owner

h-v-smacker commented May 27, 2021

What if we really, really like dollars? The taste of them, the schmell of them, the texture?

@Wuzzy2
Copy link
Author

Wuzzy2 commented May 27, 2021

Well, this mod only uses Minegeld, not dollars. And "Mg" is the official sign of Minegeld, not "$".
That's why.

@Montandalar
Copy link

The variant spelling MineGeld is widely used on LinuxForks and the symbol used is always MG; I mean the text typography on the note clearly has an uppercase G. In any case, I believe the correct solution is to ask the Unicode consortium for a "Minegeld currency symbol" and use that, or else add a Minegeld symbol to the default fonts shipped with Minetest as a Unicode private range character.

Just kidding about the currency symbol, but anyway does the $ really cause problems?

@Wuzzy2
Copy link
Author

Wuzzy2 commented Sep 19, 2022

The currency mod itself which introduces Minegeld uses "Mg", so that's pretty much official and hard to argue with.

The $ causes problems because it triggers me every time I see it. :D
Minegeld is NOT dollars, it's Minegeld!

Will be fixed in #8.

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 a pull request may close this issue.

3 participants