<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 24/09/2015 20:56,
<a class="moz-txt-link-abbreviated" href="mailto:suburbanstudio@runbox.com">suburbanstudio@runbox.com</a> wrote:<br>
</div>
<blockquote cite="mid:5604476F.4000106@runbox.com" type="cite">tuttavia
in alcuni casi con abbreviazione in maiuscolo, del tipo " M.
BRIGNONE"<br>
la funzione rende questo risultato "M.brignone" e non quello
auspicato di<br>
"M.Brignone".<br>
</blockquote>
<br>
...la causa è da ricercare nella mancanza di spazio nel database
primario tra l'abbreviazione ed il nome <br>
<br>
<i>M.BRIGNONE vs M. BRIGNONE<br>
<br>
POORLY FORMATTED DATA.... (si trattata del database della Regione
Liguria )<br>
<br>
<br>
<a class="moz-txt-link-freetext" href="http://hub.qgis.org/issues/7611">http://hub.qgis.org/issues/7611</a><br>
Aggiornato da Borys Jurgiel oltre 2 anni fa<br>
Maybe my example was too abstract, better one would be POI names
that are sometimes acronyms. I prefer to be forced to use the two
functions capitalize(lower(lga_name)) over having no way to
preserve acronyms. Of course the best would be to have both
capitalize() and title().<br>
But maybe it's not so important. Usually I have the luck to work
on properly prepared data, so I don't have much experience with
correcting poor data at this stage. I don't insist anymore :)<br>
Aggiornato da Nyall Dawson oltre 2 anni fa<br>
Lucky -- Almost all the data I work with is poorly formatted!
Anyway, I think the best resolution would be renaming Title case
-> Capitalize First Letter for now, and then ideally adding a
proper "Title case" option after 2.0. We could even make it handle
fancy things like not capitalizing "a" or "the" when they're in
the middle of a string...<br>
</i>
</body>
</html>