On Donnerstag, 5. April 2018 19:45:31 CEST Thiago Macieira wrote: > On Thursday, 5 April 2018 10:32:37 PDT Berthold Stoeger wrote: > > Hi, > > > > On Donnerstag, 5. April 2018 19:28:28 CEST Thiago Macieira wrote: > > > On Thursday, 5 April 2018 10:25:37 PDT Berthold Stoeger wrote: > > > > It's fine as it is, since all C-strings are supposed to be UTF-8 > > > > encoded. > > > > The only use I see for fromLatin1() et al. would be importing data > > > > from > > > > an > > > > external source that is not UTF-8. > > > > > > If it's US-ASCII, it is valid UTF-8, but QString::fromLatin1 is slightly > > > faster. > > > > I don't understand your point. Do you suggest limiting dive-tags to > > US-ASCII? > > I'm stuck on "tag". To me that indicates an identifier, like a Git tag. But > that's apparently not what you're using it for.
Nope - think user-defined "keywords" for dives (wall-dive, shore-dive, etc.). I'm disappointed to learn that git only does 7-bit ASCII tags...? 💔☹ Berthold _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
