@odiernod - Didn't know that. It makes sense though. I'll do some reading on Firefox addons to get an idea of what I'll need to know.
Please tell me the language code for Dutch. I tried du, ne and ho to no avail.
@donhamiltontx It looks like it's nl for Dutch, if you go to your Welcome page for that language, it's in the URL (e.g. http://www.lingq.com/learn/nl/welcome/ for Dutch).
@Lyise
You are right. nl works for Dutch. Thanks for your help.
You are right. nl works for Dutch. Thanks for your help.
@ odiernod and others.. - We have now added an API method for creating a new LingQ. You can find it on our updated API page http://www.lingq.com/apidocs/. The hint language is currently set to your native language on the site. I hope you like it! Let us know how it goes.
Thanks Mark. It will make Odiernod happy and the rest of us eager to see what is done with it. :)
Not for me. Are you sure?
Yeah, the link at the bottom has changed for me. Still, it needs a better title than <no title>, eh? haha
That's what happens when you let the programmers create the pages...!
Well, you've got to say that it's an improvement from zero documentation. ;)
Be careful! Sometimes I import to the wrong language, but that's not a big problem.
So what you are doing now is trying to create lingqs on the VH and then importing them to lingq, right? I don't know what you are working on really, I got lost with the technical vocabulary.
So what you are doing now is trying to create lingqs on the VH and then importing them to lingq, right? I don't know what you are working on really, I got lost with the technical vocabulary.
Hey Diego, basically yes. I haven't heard from the developer of VH in quite a few days, so I'm not sure if he is going to let us use his code or not. I still have to familiarize myself with the development environment for Firefox addons, which could take a while, so in the mean time, I am creating interfaces between VH and LingQ and making them available on my website for people to use them sooner. Eventually all of this functionality will get wrapped up in a Firefox addon.
Ok guys, another piece of functionality for you to play with while waiting for the eventual LingQ Firefox addon. On the same page as the xml file generator there is now a tool to let you upload an exported Vocabulary Highlighter dictionary. The tool will compare the "LingQs" in the dictionary to those in your language LingQs and any that do not yet exist in your LingQ profile will be automatically added. This way you can fairly easily import your "LingQs" made outside of LingQ into LingQ. Get it?
http://www.odierno.com/lingqtools/vhlingqgenera...
Update on the VocabularyHighlighter developer, he emailed me yesterday giving me permission to "look at" the source code, however he seems intent on drafting his own usage license rather than using one of the current popular ones, so in effect it could be a while before we have "official permission" to adapt his code.
http://www.odierno.com/lingqtools/vhlingqgenera...
Update on the VocabularyHighlighter developer, he emailed me yesterday giving me permission to "look at" the source code, however he seems intent on drafting his own usage license rather than using one of the current popular ones, so in effect it could be a while before we have "official permission" to adapt his code.
I try it, but it get this mistake:
<Server Error in '/' Application.
The remote server returned an error: (404) Not Found.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Net.WebException: The remote server returned an error: (404) Not Found.>
<Server Error in '/' Application.
The remote server returned an error: (404) Not Found.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Net.WebException: The remote server returned an error: (404) Not Found.>





