starred/esp8266_deauther

Fork 0

mirror of https://github.com/SpacehuhnTech/esp8266_deauther.git synced 2026-04-26 00:05:55 +03:00

[GH-ISSUE #590] Simplified Chinese Version #185

New issue

Closed

opened 2026-02-27 23:23:34 +03:00 by kerem · 11 comments

kerem commented

2026-02-27 23:23:34 +03:00

Owner

Originally created by @josark2005 on GitHub (Sep 8, 2017).
Original GitHub issue: https://github.com/SpacehuhnTech/esp8266_deauther/issues/590

I made a version in Chinese.
Github
By the way,you can build something to support muiltpie languages and I can provide the Chinese version.

Originally created by @josark2005 on GitHub (Sep 8, 2017). Original GitHub issue: https://github.com/SpacehuhnTech/esp8266_deauther/issues/590 I made a version in Chinese. [Github](https://github.com/jokin1999/esp8266_deauther_chinese) By the way,you can build something to support muiltpie languages and I can provide the Chinese version.

kerem

2026-02-27 23:23:34 +03:00

closed this issue
added the
improvement

translation
labels

kerem commented

2026-02-28 00:00:01 +03:00

Author

Owner

@tobozo commented on GitHub (Sep 8, 2017):

Hey, thanks for your effort.

While this is very helpful for the current build chances are it may break on next release.

@spacehuhn would it make sense to maintain i10n files where all the Web UI terms are centralized at least in one default language? That would enable the possibility to select a language from the web interface and load complete or partial translation sets.
It only needs migrating the HTML/JavaScript to l10n and bootstrapping the default language that will become the template for all further languages.

@tobozo commented on GitHub (Sep 8, 2017): Hey, thanks for your effort. While this is very helpful for the current build chances are it may break on next release. @spacehuhn would it make sense to maintain i10n files where all the Web UI terms are centralized at least in one default language? That would enable the possibility to select a language from the web interface and load complete or partial translation sets. It only needs migrating the HTML/JavaScript to l10n and bootstrapping the default language that will become the template for all further languages.

kerem commented

2026-02-28 00:00:01 +03:00

Author

Owner

@josark2005 commented on GitHub (Oct 9, 2017):

I'am waiting for the update to support the language switcher.After that I can merge something which is able to this to support Chinese to this project.
By the way,in Chinese,there are too many useless things sent to my email so I may not get the update notice by github.And recently,my cause is a little heavy.But I will check it as possible as I can.

@josark2005 commented on GitHub (Oct 9, 2017): I'am waiting for the update to support the language switcher.After that I can merge something which is able to this to support Chinese to this project. By the way,in Chinese,there are too many useless things sent to my email so I may not get the update notice by github.And recently,my cause is a little heavy.But I will check it as possible as I can.

kerem commented

2026-02-28 00:00:01 +03:00

Author

Owner

@tobozo commented on GitHub (Oct 12, 2017):

Language switcher has been implemented 📦 but I has not been merged into the testing branch (yet).

Can you please test the spiffs branch.
The install procedure is the same (load the sketch and compile) but with two extra last steps added in the ReadME.

In order to add Simplified Chinese to this build you will need to create a "zh-CN.json" file in the l10n folder.

You may then copy the content of the en.json into your file so it is ready to receive translations.
⚠️ please make sure you only modify the JSON values (don't translate the property names!).

When ready, you can check that the JSON is valid and hit the Tools/ESP8266 Sketch Data Upload button in your Arduino IDE.

If everything worked fine, you may access the language switcher from the settings page.

@tobozo commented on GitHub (Oct 12, 2017): Language switcher has been implemented :package: but I has not been merged into the testing branch (yet). Can you please test the [spiffs](https://github.com/spacehuhn/esp8266_deauther/tree/spiffs) branch. The install procedure is the same (load the sketch and compile) but with two extra last steps added in the [ReadME](https://github.com/spacehuhn/esp8266_deauther/blob/spiffs/README.md). In order to add Simplified Chinese to this build you will need to create a "zh-CN.json" file in the [l10n](https://github.com/spacehuhn/esp8266_deauther/tree/spiffs/esp8266_deauther/data/l10n) folder. You may then copy the content of the [en.json](https://github.com/spacehuhn/esp8266_deauther/blob/spiffs/esp8266_deauther/data/l10n/en.json) into your file so it is ready to receive translations. :warning: please make sure you only modify the JSON *values* (don't translate the property names!). When ready, you can [check that the JSON is valid](https://jsonlint.com/) and hit the Tools/ESP8266 Sketch Data Upload button in your Arduino IDE. If everything worked fine, you may access the language switcher from the settings page.

kerem commented

2026-02-28 00:00:01 +03:00

Author

Owner

@josark2005 commented on GitHub (Oct 13, 2017):

I've just submitted a merge request,but this form is not friendly to SimplifiedChinese grammer,may be we can try to change the form into complete sentences.
The version i just submitted(& merged) was weird somewhere in Chinese,but it was easy accessible to use for Chinese.

@josark2005 commented on GitHub (Oct 13, 2017): I've just submitted a merge request,but this form is not friendly to SimplifiedChinese grammer,may be we can try to change the form into complete sentences. The version i just submitted(& merged) was weird somewhere in Chinese,but it was easy accessible to use for Chinese.

kerem commented

2026-02-28 00:00:01 +03:00

Author

Owner

@tobozo commented on GitHub (Oct 13, 2017):

Yep, some sentences are split when a <a href> link highlights a word.

{p1}<a href="/blah">{a1}</a>

I did not want to put HTML in the JSON as it is not the role of a translation to carry structure information, but could this solve the problem?

{p1}<a href="/blah">{a1}</a>{p2}

If every split text is prefixed and suffixed by a localisable string, you may use {p1} or {p2} only, or both, depending on the grammar. This would also solve direction problems for Hebrew or Arabic.

Keep in mind that when a new {property} is added to the HTML/JSON, all language files must be updated to reflect the changes, so the sooner it happens is the best.

@tobozo commented on GitHub (Oct 13, 2017): Yep, some sentences are split when a `<a href>` link highlights a word. `{p1}<a href="/blah">{a1}</a>` I did not want to put HTML in the JSON as it is not the role of a translation to carry structure information, but could this solve the problem? `{p1}<a href="/blah">{a1}</a>{p2}` If every split text is prefixed *and* suffixed by a localisable string, you may use {p1} or {p2} only, or both, depending on the grammar. This would also solve direction problems for Hebrew or Arabic. Keep in mind that when a new `{property}` is added to the HTML/JSON, all language files must be updated to reflect the changes, so the sooner it happens is the best.

kerem commented

2026-02-28 00:00:01 +03:00

Author

Owner

@josark2005 commented on GitHub (Oct 13, 2017):

Yep,thanks for your efforts.

@josark2005 commented on GitHub (Oct 13, 2017): Yep,thanks for your efforts.

kerem commented

2026-02-28 00:00:01 +03:00

Author

Owner

@tobozo commented on GitHub (Oct 14, 2017):

You may now safely delete the spiffs branch and chackout/pull the testing branch.

Do you want to implement the grammar fixtures?

All you need to do is create a {p1-suffix} or {p1-prefix} where needed in the html templates and add the new properties in the JSON l10n files.
You can assign an empty value to the other languages so the translators can leave as is or fill at will.

@tobozo commented on GitHub (Oct 14, 2017): You may now safely delete the `spiffs` branch and chackout/pull the `testing` branch. Do you want to implement the grammar fixtures? All you need to do is create a {p1-suffix} or {p1-prefix} where needed in the html templates and add the new properties in the JSON l10n files. You can assign an empty value to the other languages so the translators can leave as is or fill at will.

kerem commented

2026-02-28 00:00:01 +03:00

Author

Owner

@josark2005 commented on GitHub (Oct 15, 2017):

The unmatched things at line 24 called "Name for".Should I add "Name for-prefix" and "Name for-suffix" after or before it?

@josark2005 commented on GitHub (Oct 15, 2017): The unmatched things at line 24 called "Name for".Should I add "Name for-prefix" and "Name for-suffix" after or before it?

kerem commented

2026-02-28 00:00:01 +03:00

Author

Owner

@haoqingtianxia commented on GitHub (Nov 14, 2017):

多谢了，我翻译的时候正好有一些不懂，还有一些不知道该怎么翻译，现在全懂了

@haoqingtianxia commented on GitHub (Nov 14, 2017): 多谢了，我翻译的时候正好有一些不懂，还有一些不知道该怎么翻译，现在全懂了![image](https://user-images.githubusercontent.com/32838843/32782452-659c8754-c983-11e7-9072-9d892971fa66.png)

kerem commented

2026-02-28 00:00:01 +03:00

Author

Owner

@josark2005 commented on GitHub (Nov 14, 2017):

有些翻译还是有点问题的，专业术语不太好翻译，最新的翻译在l10n文件夹里。

@josark2005 commented on GitHub (Nov 14, 2017): 有些翻译还是有点问题的，专业术语不太好翻译，最新的翻译在l10n文件夹里。

kerem commented

2026-02-28 00:00:01 +03:00

Author

Owner

@tobozo commented on GitHub (Mar 24, 2018):

please check the next release (anytime soon) and open a new issue for any matter regarding internationalization and localization.

closing this as related to the soon-to-be old version

@tobozo commented on GitHub (Mar 24, 2018): please check the next release (anytime soon) and open a new issue for any matter regarding internationalization and localization. closing this as related to the soon-to-be old version