-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a way to specify which encoding to use when mapping? #53
Comments
That's not something I ever considered. It would be a great addition to the library. If it is an option that can get to Nokogiri, it's an option this library could support. |
Nokogiri supports giving an encoding to it http://www.nokogiri.org/tutorials/parsing_an_html_xml_document.html |
Hi, When I make a node.to_xml, the XML produced is not in UTF-8, then french accents are corrupted. (assuming node is an instance of a class 'Node include HappyMapper') I tried various things but the happymapper to_xml seems to be different from nokogiri to_xml and doesn't accept arguments which set encoding. How do I select the encoding for happymapper marshalling (objects -> xml) ? Thank you. |
I'm not sure to understand how to do it, I'm beginner in Ruby. It would be something like node.to_xml(:builder => new builder(encode("UTF8"))) ? |
I tried : nokogiriBuilder = Nokogiri::XML::Builder.new(:encoding => 'UTF-8') But it writes "#Nokogiri::XML::Builder:0x3cce640". Then I came back to : And I modified happymapper.rb at line 505 : And then it worked. Now... I have to find a way to make the same thing without modifying happymapper.rb. |
I got help on this subject, here is the line that doesn't need any change in the gem code : file.write(node.to_xml(Nokogiri::XML::Builder.new(encoding: 'UTF-8'), nil, nil).to_xml) |
@deiga what encoding did the original XML in your example have? |
@mvz unfortuantely I have no idea after 3 years of opening this issue :) |
@deiga that was to be expected :-). Thanks for responding, anyway. |
…ppyMapper is included within a class
I get messed up unicode characters when parsing, ie.
Liiketoimintayksikkö => Liiketoimintayksikk\303\266
The text was updated successfully, but these errors were encountered: