The timeline strikes me as being a little optimistic, considering the difficult nature of the problem.
In the technical document in the 1+1 section, it states they want to build a highly constrained translation device. Given the languages they want to translate, and the fact that they're in a hurry, my bet is that this system is being built so that operatives who only speak the target languages and not English can relay possible intelligence regarding terrorist threats the CIA/NSA. Therefore, its vocabulary is probably limited to common words and "threat assessment" words. If you started talking to someone about the latest fashions, it probably wonuldn't understand.
Like other such plans, task the final result to this so-called "universal translator" I will be an other device of which the escape for all the complex translation will be a morass knot-recognizable of the verbage.*
* The above was the following, translated into Italian, and then back to English again using Babelfish:
Like other such plans, task the final result to this so-called "universal translator" I will be an other device of which the escape for all the complex translation will be a morass knot-recognizable of the verbage.
Someone mod my ill-formatted comment down to -1, please.
Like other such plans, task the final result to this so-called "universal translator" I will be an other device of which the escape for all the complex translation will be a morass knot-recognizable of the verbage.*
* The above was a translation of the following from English to Italian, and then back to English again using Babelfish:
Like other such projects, I think the end result of this so-called "universal translator" will be another device whose output for any complex translation will be a barely-recognizable morass of verbage.
Second, having used many mailers which separate out attachments... Please Don't Do It! You can't easily move your mailbox, because there are a host of associated attachment files. There is ALWAYS a synchronisation issue between attachments and messages, so you end up scanning and cleaning out the attachment folder every so often to prevent dead files from accumulating.
Certainly, but in a database solution, you could have the base64 or UU for the attachment simply be a field in the database.
I would hope that any database solution would have the option to dump the database to an mbox-compatible format, and conversely to import any mbox file into the database. That way, you get the faster accesses, scalability, and organization a database provides, while also maintaining the flexibility of being able to port stuff. The only time you would experience "hanging" is during the conversion process, which would (hopefully) occur less often than a read of a large mbox file!
Slashdot Mirror
The timeline strikes me as being a little optimistic, considering the difficult nature of the problem.
In the technical document in the 1+1 section, it states they want to build a highly constrained translation device. Given the languages they want to translate, and the fact that they're in a hurry, my bet is that this system is being built so that operatives who only speak the target languages and not English can relay possible intelligence regarding terrorist threats the CIA/NSA. Therefore, its vocabulary is probably limited to common words and "threat assessment" words. If you started talking to someone about the latest fashions, it probably wonuldn't understand.
Like other such plans, task the final result to this so-called "universal translator" I will be an other device of which the escape for all the complex translation will be a morass knot-recognizable of the verbage.*
* The above was the following, translated into Italian, and then back to English again using Babelfish:
Like other such plans, task the final result to this so-called "universal translator" I will be an other device of which the escape for all the complex translation will be a morass knot-recognizable of the verbage. Someone mod my ill-formatted comment down to -1, please.
Like other such plans, task the final result to this so-called "universal translator" I will be an other device of which the escape for all the complex translation will be a morass knot-recognizable of the verbage.* * The above was a translation of the following from English to Italian, and then back to English again using Babelfish: Like other such projects, I think the end result of this so-called "universal translator" will be another device whose output for any complex translation will be a barely-recognizable morass of verbage.