Post

TBF if I understand correctly git's i18n support is mostly "using gettext to translate the porcelain outputs", which is... not super relevant in a library context? You'd likely want to do your own i18n If you're writing an app based a git library anyways.

0 reposts3 likes

Fair, I just know that if I see someone intentionally skipping internationalization or accessibility I get extra skeptical of the rest of the work. (Lacking because lack of skill set happens, but those folks are usually apologetic about the lack.)