Jump to content

GunChleoc

Community Members
  • Posts

    619
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by GunChleoc

  1. 6 hours ago, Lion.Kanzen said:

    The em haven't great difference in this matter. Because you can use px= pixels. I'm more familiar with that.

    Everybody is more familiar with px, but it is bad practice to define sizes with pixels, because it makes it harder for the user to change. For example, if I can't see very well, I might want to make the fonts bigger - if fontsize is defined with px instead of em, ex or %, this gets much harder, especially if I'm using an old browser. Of course, margins and paddings aren't that important for legibility ;)

  2. 18 hours ago, sanderd17 said:

    That's an interesting proposal. Though I wonder if it's worth the effort. Those things should either get implemented or removed.

    Since it's confusing some players, I think it might - as long as it doesn't take too long. We don't know how many alphas it will take for all of these things to get implemented or removed.

  3. 1 hour ago, sanderd17 said:

    They can be easily recognised due to their generic nature (implemented bonuses normally mention some measurements of improvement).

    But yes, those should be signalized as being not-implemented. It's a bit annoying though, as the strings have been translated in a dozen of languages, and when we change those strings, all translators have to update that string too. And then the string has to be updated again when the bonus is implemented. It's better if we can change it to the correct string (with a correct value) from the first time.

    Maybe we could have an additional text field that says "Not yet implemented" or "To be determined", or that is empty for implemented features? This would be just 1 additional string to translate, which can then be easily removed. Of course, I don't know how much effort the programming for this would be.

    • Like 1
  4. Looks interesting, a bit like Welsh :)

    I still don't believe that it's spoken in Scotland though. There is some place-name evidence of a P-Celtic language that came before Gaelic, but that's all. I studied Gaelic at uni and would have heard of it if there was a surviving tradtional P-Celtic language in Scotland.

    English-orthgraphy pronunciation notes won't help a lot though, because Celtic languages just have too many sounds in them that English doesn't have. Plus English spelling is highly ambiguous :(

    Maybe you can borrow a good microphone somewhere or record on a friend's computer?

    Writing it down in IPA would also give us precise information. Sadly, IPA isn't taught in school usually.

    • Like 1
  5. I downloaded download.icu-project.org/files/icu4c/56.1/icu4c-56_1-data.zip and checked data/lang/gd.txt. Looks like this:

    gd{    Keys{        <snip>    }    Languages{        <snip>        gd{"Gàidhlig"}        <snip>

    This is definitely correct. I don't know which ICU version you are using here though - definitely not the current one, because it shows as "gd" in my version of Syllepsis.

    Since Sokrates has done "his own translation", I don't know what has happened there. We really do need a screenshot.

  6. The name of the UI language is "Scottish Gaelic", not "Scottish Celtic". It shows up in the languages selection menu as "gd", because the ICU version needs updating to get the language name translated into "Gàidhlig".

    I have searched my translation files for "Σκωτικά" and "Scottish", and these terms to not appear.

    So, we need a screenshot or instructions on how to reproduce this.

×
×
  • Create New...