encoding error about regional_sdm HOT 10 CLOSED

@ChristopherTracey , um, nope, have not seen it. Need a little more information. If it is in knit2pdf there are details in the tex log file.

from regional_sdm.

This is probably the most relevant part of the .log

(C:\Users\Christopher\AppData\Roaming\MiKTeX\2.9\tex\latex\ucs\uni-global.def
File: uni-global.def 2013/05/13 UCS: Unicode global data
)
\uc@secondtry=\count88
\uc@combtoks=\toks17
\uc@combtoksb=\toks18
\uc@temptokena=\toks19
)
! Missing number, treated as zero.
<to be read again> 
                   B
l.54 \DeclareUnicodeCharacter{B0}{$^{\circ}$}

from regional_sdm.

Maybe related to this: yihui/knitr#1343

from regional_sdm.

I went back to the knit and call method and dropped knit2pdf and it works fine. I'm going to go with that for now and not worry about this encoding issue at this time.

from regional_sdm.

Can you send me the entire log file? I'd guess that one of the objects getting pulled from a DB has a bad character

from regional_sdm.

Especially since it is species specific

from regional_sdm.

Yeah, however, I deleted it after I got the other version working. I'll switch it back and rerun it.

It was happening across all species--could it be in Access Tracking db?

from regional_sdm.

Interesting .. I had a heck of a time moving some fields up to the SQL Server DB because of some crazy encodings in the Access DB. In this case they were all in comments fields in which text was copy-pasted from emails or other sources. Perhaps things will be cleaner now that we are grabbing data from SQL Server tables ...

from regional_sdm.

Hopefully.

from regional_sdm.

closing this for now, can re-open if the issue pops up again

from regional_sdm.