Ancestors

Written by Richard Welty on 2025-01-03 at 14:03

1/ #Internationalization effects on software development (hopefully an instructive thread)...

Salesium (my startup) is in upstate NY, launching from Albany. we are growing slowly and carefully (media buys in major metro areas are expensive.) but we are also close to the Canadian border, and are partnering with the Central NY Rotary District, so there is potential to "slop" over, particularly because adjacent Rotary Districts do span the international border.

[#]software #canada

=> More informations about this toot | More toots from nfgusedautoparts@en.osm.town

Toot

Written by Richard Welty on 2025-01-03 at 14:06

2/ my current task is simply itemizing things i need to deal with to make spanning the border ourselves viable.

A) French language support (more probably support for the dialect spoken in Quebec). i have a locale field in the DB, but there is a need to extract all messages and prompts and create a parallel set of them in the alternate language. additionally the locale field needs to be brought out to user settings and needs to be settable on user registration

=> More informations about this toot | More toots from nfgusedautoparts@en.osm.town

Descendants

Written by Richard Welty on 2025-01-03 at 14:09

3/

B) Canadian postal addresses (mostly differ on the postal code). we use a set of zip code centroids from US FHA data when we just have a zip code, and geocode.earth for full US street addresses. i can buy canadian post data on canadian postal code centroids, but i can also query geocode.earth for this data. this may not be that hard.

=> More informations about this toot | More toots from nfgusedautoparts@en.osm.town

Written by Richard Welty on 2025-01-03 at 14:11

4/

C) like locale, the country code field will need to be exposed in settings and registration.

D) hopefully stripe (our payment provider) will help us with tax handling. the docs suggest it might.

=> More informations about this toot | More toots from nfgusedautoparts@en.osm.town

Written by Richard Welty on 2025-01-03 at 14:11

5/5 i may have missed one thing here, or possibly even more. what might it be?

=> More informations about this toot | More toots from nfgusedautoparts@en.osm.town

Written by Richard Welty on 2025-01-03 at 16:32

got one more: local search is an important component of Salesium.

at a minimum, need to add country to the advanced search page and re examine the issues of setting a default location given the various approaches visitors may take to privacy settings.

=> More informations about this toot | More toots from nfgusedautoparts@en.osm.town

Written by Richard Welty on 2025-01-03 at 16:50

and another: is the French of Saint-pierre and Miquelon more similar to the French of Quebec, or the French of Paris? and is Saint-pierre and Miquelon subject to the GDPR or not (i don't think we have major GDPR issues but we will need to do a legal review of our app to have some certainty.)

=> More informations about this toot | More toots from nfgusedautoparts@en.osm.town

Written by Richard Welty on 2025-01-03 at 16:53

i see GDPR training courses offered in Saint-pierre and Miquelon, so presumably the answer is yes, GDPR compliance will be required there. i'm glad that we have chosen to emphasize privacy in our app, should be a lot less work to do there.

=> More informations about this toot | More toots from nfgusedautoparts@en.osm.town

Written by SK53 on 2025-01-03 at 17:23

@nfgusedautoparts Various things off top of my head:

• make sure currency data items can handle reasonable range (Yen is a good test, Zairean Zaire used to really try our consolidation routines in early '90s as it was around 800,000 = 1 GBP).
• possibly enable calendars by locale if relevant (critically important in 🇨🇭 because public holidays vary by commune, but significant elsewhere 🇬🇧 ).
• are there use-cases for multi-currency (vs config)? I saw lots of kludges for this in '90s.

=> More informations about this toot | More toots from SK53@en.osm.town

Written by Richard Welty on 2025-01-03 at 18:13

@SK53 we’re depending on stripe widgets for currency. If stripe does not internationalize well, that’s a big can of worms.

=> More informations about this toot | More toots from nfgusedautoparts@en.osm.town

Written by Richard Welty on 2025-01-03 at 18:15

@SK53 don’t do calendars in this version. May use external widgets or packages. Any internal storage is strictly in UTC with a time zone field. Local display is a UI issue.

=> More informations about this toot | More toots from nfgusedautoparts@en.osm.town

Written by Richard Welty on 2025-01-03 at 18:16

@SK53 the only currency handling we do is with stripe, so that’s where multi currency might appear. If stripe can’t do it, we’ll have to deal with it then.

=> More informations about this toot | More toots from nfgusedautoparts@en.osm.town

Written by SK53 on 2025-01-03 at 18:36

@nfgusedautoparts looks pretty sophisticated to me from a quick peek at some documentation

A far cry from UK firms opening one shop in Dublin & being somewhat shocked that they'd gone multi-currency (often not realising IEP ~ 0.86 GBP). Or banks having to run separate instances of their core software for each currency.

More reasonable fudges would put separate currency in a different sales region & then special logic for when it hit the accounting system.

=> More informations about this toot | More toots from SK53@en.osm.town