Arabic encoding issue with serialize nasted object
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 597
- Forks
- 223
- Avg merge
- 11h 23m
- Merged PRs (30d)
- 3
Description
I had application using psych as yaml engine with ruby v 2.1.1 and rails 3.2
the old version of rub 1.9.4 is working fine with nested arabic object with YAML::ENGINE.yamler= 'syck'
but the meta_data in ruby 2.1.1
Here the meta_data object inside section model is serialize :meta_data
and in my boot.rb is using YAML::ENGINE.yamler= 'psych'
the meta_data stored in mysql as yaml object.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the nested Arabic serialization with Ruby 2.1.1, Rails 3.2, Psych, and MySQL, then compare it with the Syck behavior shown in the issue. Done means the serialized metadata preserves the expected Arabic text and a regression case verifies it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, rails, ruby
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100