<html><body><div>Hi Murray,</div><div><br data-mce-bogus="1"></div><div>With the lsregister output, redirect it to a temp file, e.g., /path/to/lsregister -dump >/tmp/lsreg.txt</div><div><br data-mce-bogus="1"></div><div>and then scan through it with a text editor and judicious use of cmd-f to find what you're looking for. Search for the offending characters and hopefully you'll find where that's defined, and what application of plugin is responsible. The Launch Services database is basically the Mac OS equivalent of Windows' Registry, with the difference being that you can't edit it directly, you can only read it with brute force, and it's more fragile.</div><div><br data-mce-bogus="1"></div><div>Pardon the top-post, but icloud webmail destroys proper quoting.</div><div><br data-mce-bogus="1"></div><div>Adam</div><div><br>On September 29, 2020 at 7:59 AM, Murray Eisenberg <murrayeisenberg@gmail.com> wrote:<br><br></div><div><blockquote type="cite"><div class="msg-quote"><div class="_stretch"><span class="body-text-content">On 29 Sep2020, at 1:09 AM, Adam R. Maxwell via MacOSX-TeX <macosx-tex@email.esm.psu.edu> wrote:<br><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text"><blockquote type="cite" class="quoted-plain-text">On Sep 28, 2020, at 11:59 , Murray Eisenberg <murrayeisenberg@gmail.com> wrote:</blockquote></blockquote><blockquote type="cite" class="quoted-plain-text"><blockquote type="cite" class="quoted-plain-text"><br></blockquote></blockquote><blockquote type="cite" class="quoted-plain-text"><blockquote type="cite" class="quoted-plain-text">I’m seeding that (on .cls, too, not just .sty) in any Finder window I open anywhere there is such a file. For example, in subfolders of my own Documents and in every subfolder of /usr/local/texlive/2020/texmf-dist/tex/latex that I open in Finder.</blockquote></blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">The first step is to run mdls on a .sty file in Terminal and see what it gives you for kMDItemKind and kMDItemContentType (I think those are the relevant ones).</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">Once you find the kMDItemContentType, you'll probably end up having to inspect the output of lsregister to see what application or plugin is defining it. I'd guess that whatever is defining it has a localization problem with the way types are defined. On Mojave the command is:</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><blockquote type="cite" class="quoted-plain-text">/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -dump</blockquote><blockquote type="cite" class="quoted-plain-text"><br></blockquote><br><br>I ran mdls on both memhfixc.sty and memoir.cls in /usr/local/texlive/2020/texmf-dist/tex/latex/memoir. Those are two from among _all_ .sty and .cls files that now show the two Japanese (?) characters in the Kind column of Finder list view. Output included:<br><br> mdls memhfixc.sty<br> kMDItemKind = "sty"<br> kMDItemContentType = “org.tug.sty"<br><br> mdls memoir.cls<br> kMDItemKind = “cls"<br> kMDItemContentType = "org.tug.cls"<br><br>I tried next "lsregister - dump”, but the output is huge, and I have no idea what to look for or do with the output. I tried piping to, e.g., “grep org.tug.sty” but get so many lines and no hint of what to do with that.<br> <br>---<br>Murray Eisenberg murrayeisenberg@gmail.com<br>503 King Farm Blvd #101 Home (240)-246-7240<br>Rockville, MD 20850-6667 Mobile (413)-427-5334<br><br><br></span></div></div></blockquote></div></body></html>