Earlier quoted context omitted.
Some people use "type" exclusively to refer to compile-time entities. By this definition, languages that are commonly referred to as "dynamically-typed" are actually "untyped", because they have only one compile-time type, which is essentially the same as having no types.
That's confusing weak/strong with static/dynamic typing, though. (A common error.) "What To Know Before Debating Type Systems" ( http://www.pphsg.org/cdsmith/types.html ) is a pretty good introduction to types. Also, while I'm only partway through Benjamin Pierce's _Types and Programming Languages_, it's been quite good so far.
It points out in the "Static and Dynamic Types" section that what is meant by "type" in static type-systems and what is meant by "type" in dynamic type-systems are two very different concepts. From the perspective of someone interested in static "types", dynamically-typed languages don't have types at all.