Stringex fix yaml reserved words2 - #201
Conversation
|
The I skimmed all the files and seems these are the only yaml parsing errors. I saw few symbols didn't have the quotations while original ascii version of the character was quoted. But seems Quoted Ascii chars stringex/lib/stringex/unidecoder_data/x00.yml Lines 63 to 66 in cdab2e0 Some symbols aren't quoted: stringex/lib/stringex/unidecoder_data/x20.yml Lines 124 to 128 in cdab2e0 |
|
please don't be sorry for consecutive PR. i appreciate this work. thanks! |
|
please explain? thanks |
Hi again @rsl .
Seems my investigation was incomplete 😅 I missed another 2 parsing errors, sorry for the consecutive PRs 🙏
There is 2 fixes in this PR.
on-previous PR: #200
About quoting
onIn yaml,
on,offare also converted totrueandfalse.So I quoted all
onoccurences. Fortunately there was nooffunidecode.Example:
stringex/lib/stringex/unidecoder_data/x09.yml
Lines 18 to 20 in cdab2e0
About quoting
-And also yaml
- -is parsing error. So also quoted-.(
- --was not error)Example:
stringex/lib/stringex/unidecoder_data/x20.yml
Lines 66 to 69 in cdab2e0
It became
nilin originalunidecodegem and I guessstringexusesto_sto decode it and it became empty string"".'2040'.to_i(16).chr.to_asciishould become"-"stringex
to_asciimethod:unidecode
to_asciimethod: