<GetPassage xmlns:tei="http://www.tei-c.org/ns/1.0" xmlns="http://chs.harvard.edu/xmlns/cts">
            <request>
                <requestName>GetPassage</requestName>
                <requestUrn>urn:cts:latinLit:phi1002.phi001.perseus-eng2:7.9.13-7.10.3</requestUrn>
            </request>
            <reply>
                <urn>urn:cts:latinLit:phi1002.phi001.perseus-eng2:7.9.13-7.10.3</urn>
                <passage>
                    <TEI xmlns="http://www.tei-c.org/ns/1.0"><text xml:lang="eng"><body><div n="urn:cts:latinLit:phi1002.phi001.perseus-eng2" type="translation" xml:lang="eng"><div n="7" type="textpart" subtype="book"><div n="9" type="textpart" subtype="chapter"><div n="13" type="textpart" subtype="section"><p> Again, another source of ambiguity arises from leaving it doubtful in a
                            written document whether a syllable is long or short. <hi rend="italic">Cato,</hi> for example, means one thing in the nominative when its
                            second syllable is short, and another in the dative or ablative when the
                            same syllable is long. <note anchored="true" place="unspecified"><hi rend="italic">sc.</hi> of the adjective catus, shrewd. </note>
                            There are also a number of other forms of ambiguity which it is
                            unnecessary for me to describe at length. </p></div><div n="14" type="textpart" subtype="section"><p> Further, it is quite unimportant how ambiguity arises or how it is
                            remedied. For it is clear in all cases that two interpretations are
                            possible, and as far as the written or spoken word is concerned, it is
                            equally important for both parties. It is therefore a perfectly futile
                            rule which directs us to endeavour, in connexion with this <hi rend="italic">basis,</hi> to turn the word in question to suit our
                            own purpose, since, if this is feasible, there is no ambiguity. </p></div><div n="15" type="textpart" subtype="section"><p> In cases of ambiguity the only questions which confront us will be,
                            sometimes which of the two interpretations is most natural, and always
                            which interpretation is most equitable, and what was the intention of
                            the person who wrote or uttered the words. I have, however, given
                            sufficient instructions in the course of my remarks on <hi rend="italic">conjecture</hi> and <hi rend="italic">quality,</hi> as to the
                            method of treating such questions, whether by the prosecution or the
                            defence. <pb n="v7-9 p.163"/>
                     </p></div></div><div n="10" type="textpart" subtype="chapter"><div n="1" type="textpart" subtype="section"><p> There is, however, a certain affinity between all these <hi rend="italic">bases.</hi>
                        <note anchored="true" place="unspecified">III. vi. 54.</note> For in <hi rend="italic">definition</hi> we
                            enquire into the meaning of a term, and in the <hi rend="italic">syllogism,</hi> which is closely connected with <hi rend="italic">definition,</hi>
                        <note anchored="true" place="unspecified">See ch.
                                viii. 1.</note> we consider what was the meaning of the writer,
                            while it is obvious that in the case of contrary laws there are two <hi rend="italic">bases,</hi> one concerned with the <hi rend="italic">letter,</hi> and the other with the <hi rend="italic">intention.</hi> Again, <hi rend="italic">definition</hi> is in
                            itself a kind of <hi rend="italic">ambiguity,</hi> since it brings out
                            two meanings in the same term. </p></div><div n="2" type="textpart" subtype="section"><p> The <hi rend="italic">basis</hi> concerned with the <hi rend="italic">letter</hi> and the <hi rend="italic">intention</hi> of the law
                            involves a legal question as regards the interpretation of the words,
                            which is identical with the question arising out of <hi rend="italic">contrary laws.</hi> Consequently some writers have asserted that
                            all these <hi rend="italic">bases</hi> may be resolved into those
                            concerned with the <hi rend="italic">letter</hi> and <hi rend="italic">intention,</hi> while others hold that in all cases where the <hi rend="italic">letter</hi> and the <hi rend="italic">intention</hi>
                            of a document have to be considered, it is <hi rend="italic">ambiguity</hi> that gives rise to the question at issue. But all
                            these <hi rend="italic">bases</hi> are really distinct, for an obscure
                            point of law is not the same as an ambiguous point of law. <hi rend="italic">Definition,</hi> then, </p></div><div n="3" type="textpart" subtype="section"><p> involves a general question as to the actual nature of a term, a
                            question which may conceivably have no connexion whatsoever with the
                            content of the case in point. In investigations as to the <hi rend="italic">letter</hi> and the <hi rend="italic">intention,</hi>
                            the dispute turns on the provisions contained in the law, whereas the
                                <hi rend="italic">syllogism</hi> deals with that which is not
                            contained in the law. In disputes arising out of <hi rend="italic">ambiguity</hi> we are led from the ambiguous phrase to its
                            conflicting meanings, whereas in the case of <hi rend="italic">contrary
                                laws</hi> the fight starts from the conflict of their provisions.
                        </p></div></div></div></div></body></text></TEI>
                </passage>
            </reply>
            </GetPassage>