[bisq-network/bisq-website] [WIP] Remove flags in locale selector (#243)

[Steve Jain]

@erciccione I realize you've now closed this pull request, but I meant to respond before.

Example:

Assume Spanish translation is complete, and locale-specific information is available for Mexico and Spain.

1. Focus on languages would yield a Spanish website readable by users in Mexico, Spain, and Argentina, but without the ability to show payment methods unique to any of those places.

2. Focus on locales yields a Spanish website that shows payment methods unique to Mexico (Spanish MXN) and Spain (Spanish EUR), but with no option for a Spanish website for those in Argentina (Spanish ARS).

I hope it's clear from the scenarios above that neither approach is ideal. But given the need for the Bisq website to provide locale-specific information, I find (2) more attractive. Absent this need, we could easily do (1) as you suggest...BTCPay does this and gets by just fine.

I think the problem in (2) is solved by keeping a base translation of the English website without any locale-specific items, so that it can be deployed for new locales whenever needed. This is what translators are doing right now anyway.

As long as these base translations continue to be maintained, I don't think there will be too much extra work. If a locale-specific maintainer goes MIA, we can just revert to the base translation.

This may not be a perfect long-term solution, but I think it's sufficient for the foreseeable future.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq-website/pull/243#issuecomment-531095269
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190912/20f9efc0/attachment-0001.html>