Re: VMs: Pair transcription of f80r, para 1...

[Nick Pelling <incoming@xxxxxxxxxxxxxxxxx>]

Hi Ed,

> I cut and paste your pairefied expanded transcription in to the program 
> ReadPlease which read out loud the transcription. After listening to it 
> IMHO sounds like a chant that is spelling out sounds or letters one at the 
> time. The sound does not appear stationary random, rather seems to evolves 
> from start to end.
>
> I then cut and paste in to a text editor and removed all the - characters 
> from the transcription. Again pasted the results in to the reader, now the 
> sound is more like a language, but the language is made from words that 
> are rather longish, with many syllables, it never the less seems to be 
> conveying something, if that makes sense. I realize that this involves 
> questions regarding the word separators; but the f80r transcription would 
> be more familiar if the words were still shorter.

All my pairified transcription is trying to do is look through the current 
transcription to the real transcription underneath: the way I currently 
interpret it, ISTM that individual letters in the original text are often 
represented by pairs (or small groups) of letters/glyphs in the text as we 
see it.

I also strongly suspect that there are other abbreviatory mechanisms (like 
contraction, and truncation) going on - Mark Perakh's web-page (mentioned 
here recently) postulates the main differences between A and B languages in 
terms of A being the same as B but more abbreviated, so this basic idea is 
far from new.

For example, from my transcription, you might see:
        dy-op-chee

My "dictionary" for understanding this looks like:-

        dy      = single letter from the current cipher
        op      = single letter from the current cipher
        ch      = "abbreviate", ie predict the rest of the root
        ee      = a particular word ending  (like -ibus or whatever)

In English, this might come out something like:-

        S-A-[...]-ly

In context, this might well be "safely" - but if the word was shorter (say, 
"SADLY"), I'd perhaps expect to have seen the author embellish the <ch> 
with a loop (perhaps placed towards the left edge, to indicate a shorter 
word than the one you'd initially predict).

In terms of kabbalistic codes and word/letter games, this is verging on 
"notarikon" (where single letters code for entire words), though perhaps 
pulling back from that particular brink of ambiguity.

So: the next stage isn't so much to read out my transcription (it's still 
in EVA, after all), but to suggest single letter replacements for the pairs 
- like "E" for <dy>, etc - and to see if short sections (or even long 
sections) in it are suggestive of plaintext.

For words to try this out on, I'd look for long-ish sequences which contain 
one or less <aiin>'s, such as <k-y-qo-k-al-d-am-p-aiin-she> - this might 
well contain someone's name, for example, which wouldn't be suitable for 
abbreviation - and think about what the replacement cipher might be.

Cheers, .....Nick Pelling..... 


______________________________________________________________________
To unsubscribe, send mail to majordomo@xxxxxxxxxxx with a body saying:
unsubscribe vms-list