822194a76aaec283cb1699653d5ad3433c7e44ba mspeir Thu Apr 24 16:20:58 2025 -0700 adding FAQ entry about special characters in labels, adding links to that FAQ to short/longLabel entries in trackDbDoc, and fixing minor formatting error with maxWindowCoverage section, refs #35003 diff --git src/hg/htdocs/FAQ/FAQcustom.html src/hg/htdocs/FAQ/FAQcustom.html index 6bcf1c18187..f10d4d45652 100755 --- src/hg/htdocs/FAQ/FAQcustom.html +++ src/hg/htdocs/FAQ/FAQcustom.html @@ -10,30 +10,31 @@
Return to FAQ Table of Contents
To create an annotation track that will display on the Genome Browser, you must first organize your data into a format supported by the browser custom track feature: GTF, GFF, BED, @@ -165,17 +166,27 @@
As of 2018, you can upload a custom track that contains either UCSC-style chromosome names (e.g. 'chr1', 'chrX') or one of several supported aliases, typically from Ensembl (e.g. '1' or 'X'), GenBank (e.g. 'CM000663.2' or 'CM000685.2'), or RefSeq (e.g. 'NC_000001.11' or 'NC_000023.11'). Many different custom track types support this, including BED, BAM, and any of our big* formats like bigBed or bigWig. You can view the list of supported aliases by clicking on the "View sequences" link for your assembly of interest from the Assembly Gateway page or as a "chromAlias.txt" file from our downloads server under the link "Genome sequence files and select annotations" for that assembly. + +
+The Genome Browser supports a limited set of characters in the track image. In
+addition to the characters a-z
and A-Z
, it supports
+some accented characters such as é
or á
and apostrophes,
+specifically "ʹ
" (which corresponds to Unicode character U+2019).
+If there are characters in your track's short or long label that we don't
+currently support, contact us.