I don’t have any inside knowledge of Coda’s plans here (in spite of the badge on my avatar), but here’s my armchair midgame analysis:
Coda wasn’t built with i18n in mind. Even in the early days, I remember struggling with time zones because it became apparent that nobody on the team had tried using Coda outside of California (events would show up on wrong dates in calendar view if you were East of Pacific Standard Time).
My hunch is that, in that startup-y rush to get an MVP to market, i18n was parked as a “we’ll add it later” concern - which is totally reasonable! But I suspect that some architectural choices were made early on without consideration of what eventual internationalization would require, and now it’s very difficult to bolt it on after the fact.
Now, perhaps I’m wrong (after all, Coda is full of startlingly good architectural decisions that still serve it well in use cases far beyond what was originally envisioned). Maybe Coda is successfully selling plenty of European enterprise subscriptions, and internationalization is just not big enough a pain point to warrant the resources.
If you agree that Coda’s America-centricity could use some foreign flair, please let these cowboys know by voting for all of these feature requests:
(events would show up on wrong dates in calendar view if you were East of Pacific Standard Time).