texshade: how to change fontshape of sequencelogo's

Question

I realize this is a very specific question about a certain package: texshade, but I also realize that some of the users here also use this package and might be able to help me out

I have made a multiple sequence alignment, and show only the sequence logo:

\documentclass{article}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\usepackage{texshade}

\begin{document}
\begin{texshade}{sample.aln}
\setfamily{numbering}{sf}
\setfamily{names}{sf}
\setfamily{residues}{sf}
\setfamily{features}{sf}
\setfamily{featurestyles}{sf}
\setfamily{hideblock}{sf}
\setfamily{legend}{sf}
\hideconsensus
\hidenumbering
\hideseqs
\showsequencelogo{bottom}
\end{texshade}
\end{document}

As you can see in this example I have tried to set every possible font feature to the sans serif font. However the sequence logo itself is still depicted as a rm font. The labels in the logo (such as the word "logo") are correctly changed to the SF font.

I suspect currently loaded mathfont is used to render the sequencelogo?

NOTE:actual fontspec fontselection not shown.

sample ALN file can be downloaded here

Answer 1

Wow. 14666 lines of almost undocumented code makes for a debugging headache. The source of your problem is two lines in texshade.sty in which the fontfamily cmss is explicitly called, instead of the \sfdefault. This causes the font to be substituted when used with XeLaTeX. Since these lines are in very large macro definitions, it's not practical to just give you a couple of extra lines to add to your preamble. Instead, make a copy of texshade.sty and place it in your local texmf folder. Then make the following changes:

Line 12833

\fontfamily{\sfdefault}\fontseries{m}\fontshape{n}\selectfont% changed cmss to \sfdefault

Line 14049

\fontfamily{\sfdefault}\fontseries{m}\fontshape{n} % changed cmss to \sfdefault

This should solve the problem. (If for some reason these line numbers don't correspond, you need to change any instances of cmss to \sfdefault in the file.)

Be aware that by using a local copy, any updates to the package will not be reflected in your copy, so if the package changes, you'll need to reapply the fix. (Or better yet, report it to the author, and ask him to make a change.)