Javier, do you have the curl command for this? We can just add a test case and fix it. Thanks!
Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Wed, Jul 20, 2011 at 10:28 PM, Javier de la Rosa <[email protected]> wrote: > Hi all, > > I'm trying to implement full support for unicode in my neo4j Python > REST client, but I'm finding some dificulties: > - I send a property key such as "p r öp€rtŷ", and I'm able to get > everything working using a URL encoding, that converts that string > into "'p%20r%20%C3%83%C2%B6p%C3%A2%C2%82%C2%ACrt%C3%85%C2%B7'" and all > I have to do is decode at reception. > - I send a property key such as "pr/öp€rtŷ", I can use safe URL > encoding to avoid crash with the slash: > "pr/%C3%83%C2%B6p%C3%A2%C2%82%C2%ACrt%C3%85%C2%B7", after that I can > decode it in the client. > - But if I have a property key with both slash and spaces, such as "p > r/ öp€rtŷ", there's no way to get this working properly. > > Any ideas? > Thanks. > > -- > Javier de la Rosa > http://versae.es > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
