tyiu on Nostr: Those are fair tradeoffs and I think they’re reasonable. My view is that it’s ...
Those are fair tradeoffs and I think they’re reasonable. My view is that it’s most easiest to i18n at the start of the project. If not, it gets progressively harder. But once i18n is done, it’s pretty straightforward to follow the established patterns for dealing with user-facing strings, and localization mostly comes for cheap afterward (to the developer at least - they just need to maintain the translation pipeline and ensure enough context is provided for each string). At that point, you just need to rely on the community to translate strings, if they care about wanting the client to be in their language.
Published at
2024-04-24 18:23:01Event JSON
{
"id": "819e64976aea627b75309123ca82f3afb2c9b45373404223401effab602c36fc",
"pubkey": "2779f3d9f42c7dee17f0e6bcdcf89a8f9d592d19e3b1bbd27ef1cffd1a7f98d1",
"created_at": 1713975781,
"kind": 1,
"tags": [
[
"e",
"778d7dedea926dd9ebb052b4a055c2535446fdf409d8625762a10d739a070ecf"
],
[
"e",
"43735c1b4b6bb93ce2d6bbbc7cba61a36d8f53fb7cdeeaf9613d3f324b23095d"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
]
],
"content": "Those are fair tradeoffs and I think they’re reasonable. My view is that it’s most easiest to i18n at the start of the project. If not, it gets progressively harder. But once i18n is done, it’s pretty straightforward to follow the established patterns for dealing with user-facing strings, and localization mostly comes for cheap afterward (to the developer at least - they just need to maintain the translation pipeline and ensure enough context is provided for each string). At that point, you just need to rely on the community to translate strings, if they care about wanting the client to be in their language.",
"sig": "c6f6284289cfab14949f0b3f6747bf1763ebf241181f203f816e28f37a583992c88c6cb49f95f47582f37ff83899aecbf55cbdb2d50d1c0483071d456c198728"
}
