Junwei Wang writes:
> When exporting orgmode file into HTML file, the exporter "mistakely" > consider "AC:" as some keyword for linking and the string following > "AC:" would be something link to. It looks like org-ref is setting up these links for you. Here's the relevant bit from the configuration you included: org-link-parameters '([...] ("Ac" :follow or-follow-acronym :face org-ref-acronym-face :help-echo or-acronym-tooltip :export #[771 "\211\301>\203\302\303\300A#\207\302\304\226\"\207" [("Ac" . "Gls") (latex beamer) format "\\%s{%s}" "%s"] 7 "\n\n(fn PATH _ FORMAT)"] ) ("ac" :follow or-follow-acronym :face org-ref-acronym-face :help-echo or-acronym-tooltip :export #[771 "\211\301>\203\302\303\300A#\207\302\304\226\"\207" [("ac" . "gls") (latex beamer) format "\\%s{%s}" "%s"] 7 "\n\n(fn PATH _ FORMAT)"] [...] I suspect the uppercase "AC" being treated as a link despite it not appearing in org-link-parameters is a case-related bug somewhere in Org's link handling. While that's worth looking into, it just shifts things as far as your original example is concerned: replace "AC" with "ac", and you have the same issue that you reported. One way to make Org not treat "ac:foo" as a link is to insert a zero-width space (with, e.g., <C-x 8 RET 200B>) between "ac" and ":". (info "(org)Escape Character")