<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_ym19_1_1549758300154_18420"><span>Hi Michael, <br></span></div><div id="yui_3_16_0_ym19_1_1549758300154_18479"><span><br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1549758300154_18574"><span id="yui_3_16_0_ym19_1_1549758300154_18575">I generally agree with you. <br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1549758300154_18587"><span id="yui_3_16_0_ym19_1_1549758300154_18575"><br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1549758300154_18601"><span id="yui_3_16_0_ym19_1_1549758300154_18575">But, as far as I know (as definitely a non-linguist), the semantic cases for ae vs its ligature and for oe vs its ligature are of basically the same weight. Which is why I fell back to visual similarity when comparing them. <br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1549758300154_18630"><span id="yui_3_16_0_ym19_1_1549758300154_18575"><br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1549758300154_18629"><span id="yui_3_16_0_ym19_1_1549758300154_18575">If there is a semantic case for why one is more critical than the other, I have no problem taking that comparison instead which choosing between them. </span></div><div id="yui_3_16_0_ym19_1_1549758300154_18461"> </div><div class="signature" id="yui_3_16_0_ym19_1_1549758300154_18421">Bill Jouris<br>Inside Products<br>bill.jouris@insidethestack.com<br>831-659-8360<br>925-855-9512 (direct)</div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1549758300154_18456"><br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1549758300154_18568" style="display: block;"> <div style="font-family: Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1549758300154_18567"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1549758300154_18566"> <div dir="ltr" id="yui_3_16_0_ym19_1_1549758300154_18565"> <font id="yui_3_16_0_ym19_1_1549758300154_18569" size="2" face="Arial"> <hr id="yui_3_16_0_ym19_1_1549758300154_18602" size="1"> <b><span style="font-weight:bold;">From:</span></b> Michael Bauland <Michael.Bauland@knipp.de><br> <b><span style="font-weight: bold;">To:</span></b> latingp@icann.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Monday, February 11, 2019 6:16 AM<br> <b id="yui_3_16_0_ym19_1_1549758300154_18571"><span style="font-weight: bold;" id="yui_3_16_0_ym19_1_1549758300154_18570">Subject:</span></b> Re: [Latingp] AE, OE, and Ligatures<br> </font> </div> <div class="y_msg_container"><br><div dir="ltr">Hi Bill,<br clear="none"><br clear="none">thanks for the summary.<br clear="none"><br clear="none">I agree with you if purely looking at the visual confusability issue.<br clear="none">However, with ae vs. æ and oe vs. œ the issue is not about visual<br clear="none">sameness, at least that's what the IP argued on our phone call. They<br clear="none">said that in most languages ae and æ have the same meaning and could be<br clear="none">exchanged. I can only talk for German, and there it might be ok to write<br clear="none">ae instead of the ligature but certainly not the other way round. But to<br clear="none">be honest, I personally never used such a word in German.<br clear="none"><br clear="none">Therefore the reason to make ae and its ligature variants would be<br clear="none">purely semantic. And then we have a problem: how to decide which variant<br clear="none">relation is stronger? If all are visual, it's (more or less) easy to<br clear="none">decide which visual similarity is stronger, but there's no metric to<br clear="none">compare visual and semantic similarities with each other.<br clear="none"><br clear="none">Cheers,<br clear="none"><br clear="none">Michael<br clear="none"><br clear="none">-- <br clear="none">____________________________________________________________________<br clear="none"> | |<br clear="none"> | knipp | Knipp Medien und Kommunikation GmbH<br clear="none"> ------- Technologiepark<br clear="none"> Martin-Schmeisser-Weg 9<br clear="none"> 44227 Dortmund<br clear="none"> Germany<br clear="none"><br clear="none"> Dipl.-Informatiker Fon: +49 231 9703-0<br clear="none"> Fax: +49 231 9703-200<br clear="none"> Dr. Michael Bauland SIP: <a shape="rect" ymailto="mailto:Michael.Bauland@knipp.de" href="mailto:Michael.Bauland@knipp.de">Michael.Bauland@knipp.de</a><br clear="none"> Software Development E-mail: <a shape="rect" ymailto="mailto:Michael.Bauland@knipp.de" href="mailto:Michael.Bauland@knipp.de">Michael.Bauland@knipp.de</a><br clear="none"><br clear="none"> Register Court:<br clear="none"> Amtsgericht Dortmund, HRB 13728<br clear="none"><br clear="none"> Chief Executive Officers:<br clear="none"> Dietmar Knipp, Elmar Knipp<div class="yqt7846935293" id="yqtfd25464"><br clear="none">_______________________________________________<br clear="none">Latingp mailing list<br clear="none"><a shape="rect" ymailto="mailto:Latingp@icann.org" href="mailto:Latingp@icann.org">Latingp@icann.org</a><br clear="none"><a shape="rect" href="https://mm.icann.org/mailman/listinfo/latingp" target="_blank">https://mm.icann.org/mailman/listinfo/latingp</a><br clear="none"></div></div><br><br></div> </div> </div> </div></div></body></html>