Really interesting read on i18n.

I always think of implementing i18n as incremental effort. What this post has mentioned is definitely a worth noting while preparing UI with complex grammar but implementing languages is always with 1-2 languages and then market expansion follows and we pick up more languages.

Such deep dive in linguistics is definitely a good plus along with good understanding of i18n tools/libraries.

What translation managers do you know/use that helps in aiding with the complexities of particular grammar?

This is really interesting, how do you overcome the acoustic differences of different key board and also the pressure differences among users

Above post is general introduction on JAM Stack and Jargon related to it.

Though I got to thinking that there is a part of community which does not prefer to use JAM Stack.

Please share your dislikes or complications about JAM Stack

TLDR; create a new Repo with the same name as your Github username

It will never be off from the Control Center

These differences exist because of the freedom given to everybody about their choice. So countries make their operating standard and citizens follow it.

It is simple to think that this format would work but the people who are not familiar with this format will be completely lost with it. People who are not educated but somehow learnt to follow one format; ask them to learn a new format; it will be so complicated.

This is like arguing that nobody should adopt the meter because each country has their local feet, yards, furlongs, cubits, els, steps, rods, lacters, and canas. I mean think about it: countries decide their units of measurements and their citizens follow it. It's freedom!

Sigh...

You're not even from the United States, so you should full well know how important standardisation is across country borders. There are literally only three countries that haven't adopted metric, zero that haven't adopted the standard 24 hour / 60 minute day, and only four that haven't adopted the Gregorian calendar[1].

So why is it so hard to accept the one consistent date format? Seriously? Why?

Tell you what: If you can tell me which day the following date represents, I'll give you USD 100. Seriously. I'm not even kidding.

    03/04/05

Go ahead. Guess.

[1] https://en.wikipedia.org/wiki/Civil_calendar

It is a Tuesday(1)

(1) standard probabilities apply.

But seriously, yes. I am French and write the date as 2009-03-01 and get weird looks.

I work in a French company and some people seem to assume that it is fancy to use a US format for the dates. I refuse to read a document which did not have an obvious format.

Heck, even MAR/01/2020 could be acceptable but why? Why?

Author of the post here; the gist of above post:

You can use Date.prototype.toLocaleString and its customizable API to get the localized output easily. Like in the following example, we will use the Locale String to easily get the Readable Date desired by the user

Last I checked the formatting results of toLocaleString differ between browsers and NPM for certain locales. A quick search finds a handful of issues on Github about it, but I'm pretty sure there's a more in-depth stack overflow discussion too. I'm not sure if this will all be superseeded by the new date handling proposals or not, but it's something to be wary of.

I would think that https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... would be a better choice. That said, I expect localization to just always be broken.

Title of the article: "You don't need Libraries for internationalization (i18n) of Dates"

Actual content: "... you might not need any of these libraries [moment, dayjs, date-fns] to have some basic Formatting and Localization on the Date Objects."

There you go: https://www.electron.build/multi-platform-build

Yes I’ve seen that but in practice it’s not that easy to set up. I might sound lazy but for electron being a simple way to distribute cross platform apps it is harder than I thought. That might be the OS”s fault as much as anything. WiX and all that are tricky to use too which I think this would ultimately use for Windows.

Maybe you can look into the build scripts of some opensource tools built on top of electron.

I know one from GhostCMS; Desktop tool for editing the posts: https://github.com/TryGhost/Ghost-Desktop

Thanks that looks like an extensive implementation. I’ll try it when I’m back on a pc! Not sure that their Travis.yml runs it and therefore how or where from you run the packaging scripts.

Any other way that you know and wanna share with others?