The light rays coming in from a 135/2.8 @ f/4-22 would be the same as a 135/4 @ f/4-22 and that lens is on the codable list. I'm as certain as I can be that the issue is related to focusing accuracy,
This makes no sense. The 2.8/135, which is in, requires even more focusing accuracy than the 3.4/135, which is out. The reason must have something to do either with the optical characteristics of the Telyt's construction or with the lens coding system.
(
Edit: I forgot that the 2.8/135 has googles. So the accuracy argument does make sense. But then again, in 2006 who would use a 180 mm FOV lens on a rangefinder at all?)
I'm interested in the specifics of the coding system because that will be interesting when adapting screw mount lenses to the M8. The system apparently supports lenses with at least eight focal lengths (135, 90, 75, 50, 35, 28, 24, 21), possibly some more (a 15 or 17, maybe), and five different opening apertures (1, 1.4, 2, 2.8, 4, note that only full apertures are supported). Not every single of these combinations makes sense, of course. It could also be that the system has extra provisions for encoding some optical parameters such as vignetting. There have to be some extra codepoints for the M macro adapter and coding the Tri-Elmar(s), too - it would be possible to have the a future Tri-Elmar announce itself differently at different focal lengths, but with the old one I don't think this would be possible. Just assigning every lens an individual codepoint would be possible, too, but that way they would have wasted 45 of their precious 64 codepoints already without presenting any new lenses at all! Maybe they simply couldn't fit the Telyt or its 3.4 opening aperture in there?
But that's a lot of speculation, of course.
Philipp