Re: [Virtuoso-users] LOD encoding problems

Fixed version: public static string FixLgdString(string lgdString) { byte[] lgdStringBytes = Encoding.UTF8.GetBytes(lgdString); if (lgdStringBytes.Length == lgdString.Length) return lgdString; int firstByteOffset = (194 + 144 + 195) - 208;

Re: [Virtuoso-users] LOD encoding problems

Richards, thank you for posting your ideas concerning LGD incorrectly encoded strings. I didn't want to solve this problem for a long time because hoped that fixed LGD dataset will be released before our service launch. Looks like I was too optimistic... So here I will share my solution (more worka

Re: [Virtuoso-users] LOD encoding problems

Well, I'm not affiliated with Linked Geo Data, but have already looked at way too many RDF-related encoding problems in my life, so why not look at one more ... It is indeed a problem in Linked Geo Data. The Moscow resource http://linkedgeodata.org/triplify/node/27503927 has the following

Re: [Virtuoso-users] LOD encoding problems

Hi Mitko/Alexander, Perhaps someone on the Linked Geo Data group I have added to this reply, can comment ? Best Regards Hugh Williams Professional Services OpenLink Software Web: http://www.openlinksw.com Support: http://support.openlinksw.com Forums: http://boards.openlinksw.com/support Twitter

Re: [Virtuoso-users] LOD encoding problems

The problem is in LinkedGeoData dataset. Can be reproduced with : ttlp (http_get ('http://linkedgeodata.org/triplify/node/27503927'), '', 'http://linkedgeodata.org/triplify/node/27503927'); and query : select * where { ?y ?z . } Best Regar

Re: [Virtuoso-users] LOD encoding problems

Hm... Look at this query results: SELECT ?s ?p ?o ?name WHERE { ?s ?p ?o . ?s a . ?o bif:contains '"moscow"' . OPTIONAL { ?s ?name } } Do you see "Москва" as name? I see some strange symbols despite I se

Re: [Virtuoso-users] LOD encoding problems

I'm very sorry for false alarm. The source of the problem was unicode fonts absense at my Windows 7. 2010/3/17 Mitko Iliev > Hi Alexander, > > The sparql endpoint returns UTF8, also the experiments shows proper > encoding, for example try to execute : > SELECT ?o WHERE {

Re: [Virtuoso-users] LOD encoding problems

Hi Alexander, The sparql endpoint returns UTF8, also the experiments shows proper encoding, for example try to execute : SELECT ?o WHERE { rdfs:label ?o . filter (lang(?o) = 'ru' ) } or SELECT ?o WHERE { ?s ?p ?o . ?o bif:contains '"Москва"' } limit 100

Re: [Virtuoso-users] LOD encoding problems

Hi Hugh, As I remember ADO.NET encoding bug was fixed (I haven't checked because it has no sense while other Entity Framework bug you know about is not fixed). But this problem has no relation to ADO.NET. As I haven't yet deployed my application to Amazon EC2, I execute geo queries using lod.open

Re: [Virtuoso-users] LOD encoding problems

Hi Alexander, Correction to my previous mail as I see your email from 10th March asking if all lod data is in UTF-8 mode. Yes it should be, although still are you using the ADO.Net Provider for access the LOD data or querying the SPARQL endpoint directly, as their are still encoding issues to b

Re: [Virtuoso-users] LOD encoding problems

Hi Alexander, Is this the encoding issue with the ADO.Net Provider you reported previously as that is the only one I am aware of, which is still to be resolved ? Note, their is a 40K limit on the size of emails to this mailing list thus your mail with attachment which exceeded this limit was wi

[Virtuoso-users] LOD encoding problems

Hello! I have already asked about LOD encoding problems before but no feedback followed. To be more expressive I have attached my application's screen shots with information about Manchester (english symbols - everything is okay) and Moscow (russian symbols are displayed incorrectly). Regards, Al