mirror of
https://github.com/SpacehuhnTech/esp8266_deauther.git
synced 2026-04-26 00:05:55 +03:00
[GH-ISSUE #909] [RTL] Hebrew #392
Labels
No labels
best of
bug
development
discussion
documentation
duplicate
feature request
help wanted
help wanted
improvement
pinned
pull-request
question
stale
translation
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/esp8266_deauther#392
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @itsik-b on GitHub (Jul 3, 2018).
Original GitHub issue: https://github.com/SpacehuhnTech/esp8266_deauther/issues/909
I've translated lang file for HEBREW language. I've managed to create the he.lang.gz file and created the webfile.h with the webConverter.py utility.
but it doesn't seem to work. I've set the WEBSPIFFS option in SETTINGS and confirmed that the file he.lang.gz copied to SPIFFS.
What am I missing ?
he.lang.gz
he.lang.txt
@tobozo commented on GitHub (Jul 3, 2018):
Some of the slashed quotes are mistyped (found one with a space between / and "), this makes the JSON parsing fail and the webUI loads the default language.
You can use this tool to pre-validate your JSON.
Or lazy fix: replace all slashed " quotes by directional signs such as « and »
@itsik-b commented on GitHub (Jul 3, 2018):
I removed all escape signs... still not good.
I've tried to change to RU lang, didn't change either, may be the problem is the lack of support on utf-8 files ?
@tobozo commented on GitHub (Jul 3, 2018):
Please submit your changes so we can cross-verify (i.e use gist or json validator online or pastebin).
I doubt there's a problem with utf8 otherwise we'd already know.
If the file is valid JSON and correctly zipped then it's a full browser problem, but I guess you already have Hebrew installed on the phone you're using to test this, right ?
One way to test the ESP is doing its part is to directly access the he.lang(.gz) file from your mobile browser.
Another lazy test: overwrite a language file you know is working (e.g. German) with the hebrew file, then load this language from the webUI, and tell us what you get.
@itsik-b commented on GitHub (Jul 4, 2018):
Attached the clean lang file, I can't find errors in it.
Hebrew lang installed on my browsers :) (desktop and mobile phone)
I've tested it from the ESP (http://deauth.me/web/lang/he.lang.gz) the JSON file was loaded O.K. :

he_clean.lang.txt
he.lang.gz
@itsik-b commented on GitHub (Jul 4, 2018):
got it to work. wifi.h needed to be fixed:

Now I'll be able to format it better... I'll upload the fixed lang file when I'm done.
@itsik-b commented on GitHub (Jul 4, 2018):
Is there a way to make the text right alignment ?
@tobozo commented on GitHub (Jul 4, 2018):
there are different approaches to that
html { direction: rtl; }section { direction: rtl; }span { direction :rtl; }Note that depending on the layout you sometimes have to use both directions in the same document:
Full RTL page will probably trigger the directional anomalies you usually find on LTR-only layouts, where parts are explicitely using text-align:left.
If you come to modify the css, make sure you prefix all your extra directives like this:
@itsik-b commented on GitHub (Jul 4, 2018):
I don't want to mess the other LTR languages.
I can add before every RTL text
‮(Unicode Bidirectional) which will work as RTL text.But I need to change the alignment of the paragraphs. any ideas how to do it without affecting the other LTR langs ?
@tobozo commented on GitHub (Jul 4, 2018):
the bidi byte won't fix the left/right alignment problems, and it's implicitly inserted anyway
if things are made correctly on the layout when you switch languages, all you need is CSS, you can use it in a way it won't interfer with LTR languages.
e.g.
html[lang="he"] your.directive.herein order to get the right
langattribute to the<html>tag, you need to modify a function in site.js as follows: