The following warnings occurred:
Warning [2] Undefined variable $can_link - Line: 6 - File: showthread.php(1658) : eval()'d code PHP 8.5.12 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/showthread.php(1658) : eval()'d code 6 errorHandler->error_callback
/showthread.php 1658 eval




Bad news: f116v was substantially mangled by Retracer
#20
(03-09-2025, 08:52 AM)oshfdk wrote: You are not allowed to view links. Register or Login to view.Is there any practical difference between the retracing hypothesis and the idea that the manuscript is an imperfect copy made by someone who didn't know the original language or script, hence full of mistakes?

You mean, in terms of impact on our investigations?  I think the second hypothesis would be worse.  

In both cases, the Retracer or Copyist can misread a glyph and change it into another glyph, even if it is against the rules of the language or makes no sense; or change a glyph into an invalid weirdo.  Like the s turned into o, and the Sh turned into >blip<, of my earlier "pareidolia quiz" post.

But a Copyist may also skip glyphs and words, or duplicate words and phrases.  Seems that paleographers have many name for these -- "homeoteleuton", "homeoarchy", "parablepsis", "dittography", ... Errors which the Retracer cannot make.

And a Copyist can also confuse word and character spaces. (The expression "busillis" once was popular as a term for a problem that leaves all experts baffled.  The story goes that a Latin student came across the term in a book and no Latin or history experts he consulted knew what it meant. It turned out that what he had read as "in die busillis" = "on the day of the busillis" was in fact "in diebus illis" = "in those days"...)

All the best, --jorge
Reply


Messages In This Thread
RE: Bad news: f116v was substantially mangled by Retracer - by Jorge_Stolfi - 03-09-2025, 01:19 PM
Big water stain on f116v - by Jorge_Stolfi - 05-09-2025, 10:00 PM

Forum Jump:


Users browsing this thread: 2 Guest(s)