Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Comment Solr is Lucene-based and understands Word files (Score 1) 232

The upcoming Solr 1.4 release (http://lucene.apache.org/solr) includes the Tika document parser. You can throw Word, PDF etc files to it, and it will index them for you. Solr is a web service; a few hundred lines of PHP would be enough to use the Solr to index your shared volume, and a again that much for a web-based search tool.

Space

Introducing the Warpship 361

astroengine writes "Dr. Richard Obousy, a guy who has put modern science into the warp drive, has designed his very own warpship. Now, for the first time, he's shared it with the world. It might not be the sleek Starship Enterprise, but its structure has been optimized to harness local 'dark energy,' generating a warp bubble so faster-than-light velocities are possible." Now, the only question is: will the ship achieve faster-than-light travel ... or will the company hit those speeds once it has enough money from investors?

Comment Re:Question for experts? (Score 1) 576

You said: "They could go even further and set up servers at the network borders so even dns servers still set to use the old roots would get the new ones."

Which network borders? On "the border on the Internet where France borders on the US"? That does not exist. There are a zillion places where France is connected to the rest of the Internet. And it doesn't help for people outside France that wish to find a web server in the .fr domain.

Anyway, there is hardly any need. Most people make use of their ISP's DNS servers. If those ISP's either migrate to new roots, or manually inject the .fr servers, or if the root servers outside the US take things into their own hands, the problem is over.

Comment Usability has to come first (Score 2) 189

I see a lot of people go off into the deep end with all kinds of complicated databases and transformation tools. Maybe this works for very large projects with lots op people working on them.

My experience is:

If you want to be able to translate texts in a reasonably efficient manner, you should keep small texts for multiple languages together and separate them for large texts. For instance, I use a lot of scripts that generate forms. So I start every page with an array that contains words and phrases:

if ($lang == "nl")
$texts = array("name"=>"Naam", "age"=>"Leeftijd");
else
$texts = array("name"=>"Name", "age"=>"Age");

(I include a header that figures out the user's language by the http accept language, user and site domains (none of which are foolproof) or authentication/cookie data for registered users.)

Translating this is very simple: copy the array definition and change the phrases. You don't want to use a database for this, because you need to be able to look at the from and to languages at the same time. For large texts I include html files. Translating them isn't much of a problem, keeping several versions up to date is harder.

Don't forget that many users speak more than one language. For instance, many users I talk to in Dutch on my site want to see links to content in both Dutch and English, so when they sign up they can choose between Dutch, English, Dutch + English and English + Dutch.

Slashdot Top Deals

After a number of decimal places, nobody gives a damn.

Working...