"404 Not Found" translation

[Lisa]

I saw this page today and loved it!  It's probably one of the best 404 Not Found messages I've ever seen.  

It's very clever, and they have the 404 message in Klingon as well.  But NO NA'VI!   Not good...we need to fix this.  

I don't think we have a word for page, but some of those messages don't use any specific term so perhaps we could just use this thing.

Does this work?  Or is there a better way to say it?

624ᵒ Nìkeftxo futa ngal fwerew ke lu fìtseng.
404 Sadly this thing which you are seeking is not here.

I originally had it written with fì'ut a but remembered that's futa... is that right?  

At any rate, I'd love to send the ibiblio webfolks a correct Na'vi sentence so they can add it to the page; all corrections and/or alternate sentences are very welcome.    



Update:

404 Fì'ul a ngal fwerew ke tok fìtsengit.
404 This thing which you are seeking is not here.

Thanks to Inspirata and Lance R. Casey for the corrections.  


Update 2:

And an alternative sentence from Plumps:

404 Ngal fwerew a fì'u ke fkeytok.
404 This thing which you are seeking does not exist.


Update 3: Changed the octal number back to original status code, as per omängum fra'uti's suggestion.

['Oma Tirea]

º624 (Nìkeftxo) fì'ul a ngal fwerew, ke lu tok fìtsengit.

/corrections

[Lisa]

lu tok

*head slap*   

I keep forgetting about tok.  And thanks for the other corrections.... maybe one day I'll get it right. 

[Lance R. Casey]

º624 Fì'ul a ngal fwerew, ke tok fìtsengit.

Still need agentive case in the subordinate clause, since fwew is transitive -- and I'd scrap the comma.

And whoever wrote that "Klingon" has no honor. "Information-scraper demonstrate fail utterly"? Qu'vatlh!

[Plumps]

lu tok

*head slap*   

I keep forgetting about tok.  And thanks for the other corrections.... maybe one day I'll get it right. 

There's also the 'new' fkeytok, exist Remember there is never only one way to translate something.

ngal fwerew a fì'u ke fkeytok.

[Stranger Come Knocking]

  Best 404 page EVAR.  And it comes in LOLcat.  But it needs a little work. 'All ur page r belong to us now.  U can haz 404' seems more appropriate.

[Kamean]

Hrh

[Tswusayona Tsamsiyu]

why say fì'u? I'd just say 'u.

[Sireayä mokri]

why say fì'u? I'd just say 'u.

This form seems to be more common.                                                                     

[Lisa]

There's also the 'new' fkeytok, exist Remember there is never only one way to translate something.

ngal fwerew a fì'u ke fkeytok.

Oooh, good call!  I remember seeing that word now that you mention it, but I'm (obviously) not doing a very good job keeping up with all the new vocabulary.   Tìmokìri ngeyä oe ngaru seiyi irayo! 


My first thought when I was reading your sentence was "why wasn't it fì'ut?", but after I looked at it closer I think I might understand.  Is the logic here that since nga goes with (in the same clause as?) fwew and fwew is transitive, nga gets the agentive but fì'u goes with fkeytok and fkeytok is intransitive,  so no case on fì'u?   

(ngal fwerew) a (fì'u ke fkeytok)

Hìtxoa, cases still confuse the hell out of me sometimes.   

[Tswusayona Tsamsiyu]

you're absolutely correct.

[omängum fra'uti]

A bit off-topic, but in this case I'd stick with 404, and not try to take the number 404 and turn it into octal.

The reason is it isn't a number, it's a status code.  The first digit is the type of status.  1xx = informational, 2xx = success, 3xx = redirection, 4xx = client error (IE badly formed request, document doesn't exist) and 5xx = server error.

If you convert it into octal, it loses its ability to be a status code, as now 144-309 = information, 310-453 = success, 454-619 = redirection, 620-763 = client error, and 764-1130 = server error, which makes no sense.

[Carborundum]

Where's Muzer when you need him?

[Lisa]

A bit off-topic, but in this case I'd stick with 404, and not try to take the number 404 and turn it into octal.

The reason is it isn't a number, it's a status code.  The first digit is the type of status.  1xx = informational, 2xx = success, 3xx = redirection, 4xx = client error (IE badly formed request, document doesn't exist) and 5xx = server error.

If you convert it into octal, it loses its ability to be a status code, as now 144-309 = information, 310-453 = success, 454-619 = redirection, 620-763 = client error, and 764-1130 = server error, which makes no sense.

You're absolutely right, I'd forgotten about the status code aspect.  And I agree, it does make sense to leave the digits alone.

I had sent the request to the ibiblio webfolks last night, so I'll go back and add to my request that if they can add Na'vi to their list of languages (please please please!) to ignore the octal conversion.  Thanks for bringing that up! 

[Ataeghane]

404 not found.
404 ke rolun fkol.

Not the easiest way?

[Lisa]

404 not found.
404 ke rolun fkol.

Not the easiest way?

Perhaps the easiest way but most of the messages on that page (that I could understand ) were more verbose, and I was trying to stay in that format/style.   

[Ataeghane]

Polish translation is "Takiej strony nie ma", that is: "There is no page like this". So what about: Ke l(äng)u fì... oh, no word for "page". What about fya'o?

[Tswusayona Tsamsiyu]

404 not found.
404 ke rolun fkol.

Not the easiest way?

even easier: 404 ketsukrun

[Kamean]

even easier: 404 ketsukrun

Sunu nìtxan.

[Ataeghane]

Oer kop. Sìltsan säfpìl.