Plug-ins i18n via Transifex
-
Some interesting feature requests can be found here:
https://github.com/NodeBB/nodebb-plugin-2factor/pull/93In short:
- proposal to move all language files to Transifex and allow translators to work on translating plug-ins (pre-installed/default/bundled plug-ins were mentioned),
- 123456 vs. 123 456 as common i18n problem not only for Korea and Japan,
- some other shortcomings from Korean user point of view.
Korean translation by NavyStack · Pull Request #93 · NodeBB/nodebb-plugin-2factor
First and foremost, I wish to express my sincere appreciation for the development of such an outstanding plugin. In my role as the coordinator for NodeBB's Korean and Japanese translations, I have strived to maintain consistency in wording with the primary translation project. At present, numerous default plugins of NodeBB come pre-installed. However, it appears that this applies not only to administrators but also to end-users. Therefore, it would be advantageous to enable the management of built-in plugin translations on Transifex as well. While I currently utilize NodeBB in production, there are instances where certain strings or plugins remain untranslatable, often exposing my users, who are not proficient in English, to such content. Hence, I would kindly request your consideration on this matter. Below, I have outlined several queries regarding the plugin, along with suggestions for enhancement: Some applications use a space character when presenting a 6-digit number. For instance, 123456 may appear as 123 456 when copied to the clipboard. Given the increasing prevalence of users utilizing this feature via a browser extension plugin, I believe enhancing the user experience by disregarding space characters and accepting numbers solely would be beneficial. There are instances where 2FA (Two-Factor Authentication) needs to be input more than once due to specific circumstances. For instance, upon pasting it into a browser or application, users are prompted to re-enter their username and password, even if the values are accurate. This could be due to either rapid typing or previous input. Personally, I circumvent this inconvenience by pressing and holding the CTRL key while performing CTRL + V. (But... sometimes I face Username and Password form page.)However, this workaround may prove inconvenient for the average user. While acknowledging the inherent trade-off between security and convenience, I believe there is room for improvement in this regard, particularly concerning 2FA. Occasionally, upon entering my username, password, and 2FA code, I find myself logged in as a non-member pop-up. This issue warrants attention for resolution. Your attention to these matters would be greatly appreciated, and I am confident that addressing these concerns would significantly enhance the usability and functionality of the plugin. I am currently using NodeBB in a production environment. Hence, updating without translations results in English displaying as is, akin to a bleeding edge situation. I kindly request measures to improve this. You can verify my commit timestamps, which reflect my working pace. There's ample time to pre-translate adequately for any additions. Your cooperation in presenting translation sentences prior to adding new strings would be greatly appreciated. Thanks for your support.
GitHub (github.com)