translating heiroglyphics

Reply Tue 4 Nov, 2008 09:30 pm
Isn't it possible that when doing a translation for these symbols, that the message can be mistaken due to an error in a translation?

How about do people go about translating these in the first place? Isn't some sort of "key/cipher" needed in order to figure it out? Otherwise, isn't it more or less just seeing what fits together, with many different possibilities?

For example, if say that 123 456 567 represented a sentence in another language, how would you go about translating it? Lets say this message means: The car is art. Can't it also be translated into something else?
  • Topic Stats
  • Top Replies
  • Link to this Topic
Type: Question • Score: 2 • Views: 1,915 • Replies: 3
No top replies

Reply Tue 4 Nov, 2008 09:39 pm
Rosetta Stone...yes a "key" helps a lot.

0 Replies
Reply Tue 4 Nov, 2008 11:17 pm
If memory serves I believe hieroglyphics came closer to being an alphabetic language than they anticipated. But some of the best scholars in the world had been beating their heads against a total wall with hieroglyphics prior to deciphering the Rosetta stone.

0 Replies
Reply Wed 5 Nov, 2008 01:52 am
In any translation mistakes can be made. Some translators also try to get their own message into the translation. Some translate too fast. Others don´t bother about checking if a word can have more than one meaning.
A European writes he drove 100 kilometres and the American translates it to 100 miles.
In an American book which took place in Georgia a person walks out to the Miami burial ground.
In the Swedish translation she walks out to the Miami Indian burial ground. This is correct.
In the German translation she walks down to Miami cementry. Which is absolutely wrong and also impossible. You don´t walk from Georgia to Miami in Florida and back within a couple of hours.Also there is a difference in a burial ground and a cementry.
0 Replies

Related Topics

  1. Forums
  2. » translating heiroglyphics
Copyright © 2024 MadLab, LLC :: Terms of Service :: Privacy Policy :: Page generated in 0.76 seconds on 04/18/2024 at 01:01:02