static-analysis icon indicating copy to clipboard operation
static-analysis copied to clipboard

I18N support?

Open johnfelipe opened this issue 3 years ago • 3 comments

Can I contribute if you share strings in yml, Json or pot file format for es, de, de and it

johnfelipe avatar Aug 08 '22 13:08 johnfelipe

Hey John, that's an interesting idea. However I'm not sure I fully understand. How would we use the translations in this repo? Would we list all tools multiple times in different languages? We could add internationalization support to the website, even though it would be a lot of work to maintain. Curious about your thoughts.

mre avatar Aug 11 '22 13:08 mre

If you parse all strings into yml, Json or something I want to translate in different languages

johnfelipe avatar Aug 11 '22 13:08 johnfelipe

Yes, the rendering part can certainly be done. The issue is that I don't know how to maintain the translations in the long run. For example, if someone updates a tool description, we would have to update the translations as well. I don't think most contributors would care to update them themselves, so we'd have to either remind them or do it ourselves. The other question is still how we're going to present the translations to our users. Would we render all of the different translations in the same repository or create separate repositories for them? Is there any other list on Github that does this? I'd be thankful for any links or thoughts.

mre avatar Aug 11 '22 14:08 mre

At this point I don't see how we can solve the problems mentioned in my previous comment. I think i18n would add quite a bit of maintenance overhead and I don't think we can handle it at the moment. Let's revisit this at at a later point in time. Thanks for the suggestion and the help you offered @johnfelipe. 👍

mre avatar Sep 25 '22 09:09 mre

Dear I want to be that contributor, I want to translate in my languages es, de, fr and it, strings and markdown Pls begin and I will do it for long term dear.

El jue, 11 de ago. de 2022, 9:19 a. m., Matthias @.***> escribió:

Yes, the rendering part can certainly be done. The issue is that I don't know how to maintain the translations in the long run. For example, if someone updates a tool description, we would have to update the translations as well. I don't think most contributors would care to update them themselves, so we'd have to either remind them or do it ourselves. The other question is still how we're going to present the translations to our users. Would we render all of the different translations in the same repository or create separate repositories for them? Is there any other list on Github that does this? I'd be thankful for any links or thoughts.

— Reply to this email directly, view it on GitHub https://github.com/analysis-tools-dev/static-analysis/issues/1061#issuecomment-1212053498, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADIWFEVJPEUGWSD55KWK2DVYUDXZANCNFSM555GJN5Q . You are receiving this because you authored the thread.Message ID: @.***>

johnfelipe avatar Oct 11 '22 08:10 johnfelipe