Caron Accent v{a} doesn't render without usepackage{xeCJK}












3















I am encountering an odd problem. I want to create composite characters such as ǎ using the newunicodechar package. However, it only yields a result in combination with the xeCJK package.



This code produces missing characters:



documentclass[a4paper,12pt,article,oneside]{memoir}
usepackage{fontspec}
usepackage{xunicode}

usepackage[british]{babel}

setmainfont[Ligatures=TeX]{Minion Pro}

usepackage{newunicodechar}
newunicodechar{ǚ}{v{ü}}
newunicodechar{Ǚ}{v{Ü}}
newunicodechar{ǎ}{v{a}}
newunicodechar{Ǎ}{v{A}}
newunicodechar{ǒ}{v{o}}
newunicodechar{Ǒ}{v{O}}


begin{document}

ǚ Ǚ ǎ


end{document}


If I load the xeCJK package then the characters render just fine.
Why is that? And how to generate composite characters without the named package?



Note:




  • this is reproducible with other fonts that do not contain the unicode characters (e.g. Adobe Garamond Pro)

  • Minion Pro does contain a caron character (unicode 02C7, index 136)










share|improve this question



























    3















    I am encountering an odd problem. I want to create composite characters such as ǎ using the newunicodechar package. However, it only yields a result in combination with the xeCJK package.



    This code produces missing characters:



    documentclass[a4paper,12pt,article,oneside]{memoir}
    usepackage{fontspec}
    usepackage{xunicode}

    usepackage[british]{babel}

    setmainfont[Ligatures=TeX]{Minion Pro}

    usepackage{newunicodechar}
    newunicodechar{ǚ}{v{ü}}
    newunicodechar{Ǚ}{v{Ü}}
    newunicodechar{ǎ}{v{a}}
    newunicodechar{Ǎ}{v{A}}
    newunicodechar{ǒ}{v{o}}
    newunicodechar{Ǒ}{v{O}}


    begin{document}

    ǚ Ǚ ǎ


    end{document}


    If I load the xeCJK package then the characters render just fine.
    Why is that? And how to generate composite characters without the named package?



    Note:




    • this is reproducible with other fonts that do not contain the unicode characters (e.g. Adobe Garamond Pro)

    • Minion Pro does contain a caron character (unicode 02C7, index 136)










    share|improve this question

























      3












      3








      3


      0






      I am encountering an odd problem. I want to create composite characters such as ǎ using the newunicodechar package. However, it only yields a result in combination with the xeCJK package.



      This code produces missing characters:



      documentclass[a4paper,12pt,article,oneside]{memoir}
      usepackage{fontspec}
      usepackage{xunicode}

      usepackage[british]{babel}

      setmainfont[Ligatures=TeX]{Minion Pro}

      usepackage{newunicodechar}
      newunicodechar{ǚ}{v{ü}}
      newunicodechar{Ǚ}{v{Ü}}
      newunicodechar{ǎ}{v{a}}
      newunicodechar{Ǎ}{v{A}}
      newunicodechar{ǒ}{v{o}}
      newunicodechar{Ǒ}{v{O}}


      begin{document}

      ǚ Ǚ ǎ


      end{document}


      If I load the xeCJK package then the characters render just fine.
      Why is that? And how to generate composite characters without the named package?



      Note:




      • this is reproducible with other fonts that do not contain the unicode characters (e.g. Adobe Garamond Pro)

      • Minion Pro does contain a caron character (unicode 02C7, index 136)










      share|improve this question














      I am encountering an odd problem. I want to create composite characters such as ǎ using the newunicodechar package. However, it only yields a result in combination with the xeCJK package.



      This code produces missing characters:



      documentclass[a4paper,12pt,article,oneside]{memoir}
      usepackage{fontspec}
      usepackage{xunicode}

      usepackage[british]{babel}

      setmainfont[Ligatures=TeX]{Minion Pro}

      usepackage{newunicodechar}
      newunicodechar{ǚ}{v{ü}}
      newunicodechar{Ǚ}{v{Ü}}
      newunicodechar{ǎ}{v{a}}
      newunicodechar{Ǎ}{v{A}}
      newunicodechar{ǒ}{v{o}}
      newunicodechar{Ǒ}{v{O}}


      begin{document}

      ǚ Ǚ ǎ


      end{document}


      If I load the xeCJK package then the characters render just fine.
      Why is that? And how to generate composite characters without the named package?



      Note:




      • this is reproducible with other fonts that do not contain the unicode characters (e.g. Adobe Garamond Pro)

      • Minion Pro does contain a caron character (unicode 02C7, index 136)







      xetex fontspec accents xecjk newunicodechar






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 25 at 9:58









      PaulPaul

      12718




      12718






















          2 Answers
          2






          active

          oldest

          votes


















          6














          The default setup doesn't use unicode U+02C7, but the combining accent U+030C which is missing in your font. xecjk contains some code to use U+02C7 instead, but seems to use this code only if xunicode is loaded too - which is a bit of a pain, as normally one shouldn't use it anymore.



          You can clone the xeCJK code by using add@accent. If more fonts are involved where some have the combining accent, some additional checks for glyph existence are probably needed.



          documentclass[a4paper,12pt,article,oneside]{memoir}

          usepackage{fontspec}
          usepackage[british]{babel}

          setmainfont[Ligatures=TeX]{MinionPro-Regular.otf}

          usepackage{newunicodechar}
          makeatletter

          newunicodechar{ǚ}{add@accent{`^^^^02c7}{ü}}
          newunicodechar{Ǚ}{add@accent{`^^^^02c7}{Ü}}
          newunicodechar{ǎ}{add@accent{`^^^^02c7}{a}}
          makeatother
          %newunicodechar{Ǎ}{v{A}}
          %newunicodechar{ǒ}{v{o}}
          %newunicodechar{Ǒ}{v{O}}
          %
          begin{document}
          abc

          ǚ Ǚ ǎ

          end{document}


          enter image description here






          share|improve this answer
























          • Thanks! As always you're answering my questions :) Could this be a potential feature request for newunicodechar: Substitute combining characters automatically?

            – Paul
            Feb 25 at 11:06













          • No, newunicodechar doesn't care about the code you use, you could also input a picture. But you make a feature request for latex, the kernel could perhaps add a fall back to 02c7 to the definition of v.

            – Ulrike Fischer
            Feb 25 at 11:11











          • Are you sure I can just submit it to the Latex2e github?

            – Paul
            Feb 25 at 11:34



















          3














          Based on a trick by Egreg, this uses the accent primitive. I chose to simply redefine v.



          documentclass{standalone}
          usepackage{fontspec, newunicodechar}

          usepackage[british]{babel}

          setmainfont[Ligatures=TeX]{Cardo}

          renewcommandv[1]{accentstring"02C7 #1}

          newunicodechar{ǚ}{v{ü}}
          newunicodechar{Ǚ}{v{Ü}}
          newunicodechar{ǎ}{v{a}}
          newunicodechar{Ǎ}{v{A}}
          newunicodechar{ǒ}{v{o}}
          newunicodechar{Ǒ}{v{O}}

          begin{document}

          ǚ Ǚ ǎ Ǎ ǒ Ǒ

          end{document}


          ǚ Ǚ ǎ Ǎ ǒ Ǒ



          I picked Cardo as a common font that contains the caron accent, but not the precomposed ǚ.






          share|improve this answer
























          • I can reproduce the MWE of this solution with Minion Pro. However, for some reason it doesn't work in my actual main file. There is some clash with another package, and I cannot identify (yet) which one it is.

            – Paul
            Feb 25 at 11:23











          • You might to change the documentclass back, if you didn’t. I switched to standalone for the convenience of creating a cropped image. Anyway, just adding the line renewcommandv[1]{accentstring"02C7 #1} ought to work.

            – Davislor
            Feb 25 at 11:32













          • I already checked and your solution definitely works with documentclass[a4paper,12pt,article,oneside]{memoir} Must be something else...

            – Paul
            Feb 25 at 11:34











          • I also removed xunicode? Or maybe it’s related to setmainfont versus babelfont?

            – Davislor
            Feb 25 at 11:42











          • I identified the conflicting package: it's hyperref But I have no idea what causes it

            – Paul
            Feb 25 at 12:27











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "85"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f476566%2fcaron-accent-va-doesnt-render-without-usepackagexecjk%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          6














          The default setup doesn't use unicode U+02C7, but the combining accent U+030C which is missing in your font. xecjk contains some code to use U+02C7 instead, but seems to use this code only if xunicode is loaded too - which is a bit of a pain, as normally one shouldn't use it anymore.



          You can clone the xeCJK code by using add@accent. If more fonts are involved where some have the combining accent, some additional checks for glyph existence are probably needed.



          documentclass[a4paper,12pt,article,oneside]{memoir}

          usepackage{fontspec}
          usepackage[british]{babel}

          setmainfont[Ligatures=TeX]{MinionPro-Regular.otf}

          usepackage{newunicodechar}
          makeatletter

          newunicodechar{ǚ}{add@accent{`^^^^02c7}{ü}}
          newunicodechar{Ǚ}{add@accent{`^^^^02c7}{Ü}}
          newunicodechar{ǎ}{add@accent{`^^^^02c7}{a}}
          makeatother
          %newunicodechar{Ǎ}{v{A}}
          %newunicodechar{ǒ}{v{o}}
          %newunicodechar{Ǒ}{v{O}}
          %
          begin{document}
          abc

          ǚ Ǚ ǎ

          end{document}


          enter image description here






          share|improve this answer
























          • Thanks! As always you're answering my questions :) Could this be a potential feature request for newunicodechar: Substitute combining characters automatically?

            – Paul
            Feb 25 at 11:06













          • No, newunicodechar doesn't care about the code you use, you could also input a picture. But you make a feature request for latex, the kernel could perhaps add a fall back to 02c7 to the definition of v.

            – Ulrike Fischer
            Feb 25 at 11:11











          • Are you sure I can just submit it to the Latex2e github?

            – Paul
            Feb 25 at 11:34
















          6














          The default setup doesn't use unicode U+02C7, but the combining accent U+030C which is missing in your font. xecjk contains some code to use U+02C7 instead, but seems to use this code only if xunicode is loaded too - which is a bit of a pain, as normally one shouldn't use it anymore.



          You can clone the xeCJK code by using add@accent. If more fonts are involved where some have the combining accent, some additional checks for glyph existence are probably needed.



          documentclass[a4paper,12pt,article,oneside]{memoir}

          usepackage{fontspec}
          usepackage[british]{babel}

          setmainfont[Ligatures=TeX]{MinionPro-Regular.otf}

          usepackage{newunicodechar}
          makeatletter

          newunicodechar{ǚ}{add@accent{`^^^^02c7}{ü}}
          newunicodechar{Ǚ}{add@accent{`^^^^02c7}{Ü}}
          newunicodechar{ǎ}{add@accent{`^^^^02c7}{a}}
          makeatother
          %newunicodechar{Ǎ}{v{A}}
          %newunicodechar{ǒ}{v{o}}
          %newunicodechar{Ǒ}{v{O}}
          %
          begin{document}
          abc

          ǚ Ǚ ǎ

          end{document}


          enter image description here






          share|improve this answer
























          • Thanks! As always you're answering my questions :) Could this be a potential feature request for newunicodechar: Substitute combining characters automatically?

            – Paul
            Feb 25 at 11:06













          • No, newunicodechar doesn't care about the code you use, you could also input a picture. But you make a feature request for latex, the kernel could perhaps add a fall back to 02c7 to the definition of v.

            – Ulrike Fischer
            Feb 25 at 11:11











          • Are you sure I can just submit it to the Latex2e github?

            – Paul
            Feb 25 at 11:34














          6












          6








          6







          The default setup doesn't use unicode U+02C7, but the combining accent U+030C which is missing in your font. xecjk contains some code to use U+02C7 instead, but seems to use this code only if xunicode is loaded too - which is a bit of a pain, as normally one shouldn't use it anymore.



          You can clone the xeCJK code by using add@accent. If more fonts are involved where some have the combining accent, some additional checks for glyph existence are probably needed.



          documentclass[a4paper,12pt,article,oneside]{memoir}

          usepackage{fontspec}
          usepackage[british]{babel}

          setmainfont[Ligatures=TeX]{MinionPro-Regular.otf}

          usepackage{newunicodechar}
          makeatletter

          newunicodechar{ǚ}{add@accent{`^^^^02c7}{ü}}
          newunicodechar{Ǚ}{add@accent{`^^^^02c7}{Ü}}
          newunicodechar{ǎ}{add@accent{`^^^^02c7}{a}}
          makeatother
          %newunicodechar{Ǎ}{v{A}}
          %newunicodechar{ǒ}{v{o}}
          %newunicodechar{Ǒ}{v{O}}
          %
          begin{document}
          abc

          ǚ Ǚ ǎ

          end{document}


          enter image description here






          share|improve this answer













          The default setup doesn't use unicode U+02C7, but the combining accent U+030C which is missing in your font. xecjk contains some code to use U+02C7 instead, but seems to use this code only if xunicode is loaded too - which is a bit of a pain, as normally one shouldn't use it anymore.



          You can clone the xeCJK code by using add@accent. If more fonts are involved where some have the combining accent, some additional checks for glyph existence are probably needed.



          documentclass[a4paper,12pt,article,oneside]{memoir}

          usepackage{fontspec}
          usepackage[british]{babel}

          setmainfont[Ligatures=TeX]{MinionPro-Regular.otf}

          usepackage{newunicodechar}
          makeatletter

          newunicodechar{ǚ}{add@accent{`^^^^02c7}{ü}}
          newunicodechar{Ǚ}{add@accent{`^^^^02c7}{Ü}}
          newunicodechar{ǎ}{add@accent{`^^^^02c7}{a}}
          makeatother
          %newunicodechar{Ǎ}{v{A}}
          %newunicodechar{ǒ}{v{o}}
          %newunicodechar{Ǒ}{v{O}}
          %
          begin{document}
          abc

          ǚ Ǚ ǎ

          end{document}


          enter image description here







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 25 at 10:50









          Ulrike FischerUlrike Fischer

          194k8302688




          194k8302688













          • Thanks! As always you're answering my questions :) Could this be a potential feature request for newunicodechar: Substitute combining characters automatically?

            – Paul
            Feb 25 at 11:06













          • No, newunicodechar doesn't care about the code you use, you could also input a picture. But you make a feature request for latex, the kernel could perhaps add a fall back to 02c7 to the definition of v.

            – Ulrike Fischer
            Feb 25 at 11:11











          • Are you sure I can just submit it to the Latex2e github?

            – Paul
            Feb 25 at 11:34



















          • Thanks! As always you're answering my questions :) Could this be a potential feature request for newunicodechar: Substitute combining characters automatically?

            – Paul
            Feb 25 at 11:06













          • No, newunicodechar doesn't care about the code you use, you could also input a picture. But you make a feature request for latex, the kernel could perhaps add a fall back to 02c7 to the definition of v.

            – Ulrike Fischer
            Feb 25 at 11:11











          • Are you sure I can just submit it to the Latex2e github?

            – Paul
            Feb 25 at 11:34

















          Thanks! As always you're answering my questions :) Could this be a potential feature request for newunicodechar: Substitute combining characters automatically?

          – Paul
          Feb 25 at 11:06







          Thanks! As always you're answering my questions :) Could this be a potential feature request for newunicodechar: Substitute combining characters automatically?

          – Paul
          Feb 25 at 11:06















          No, newunicodechar doesn't care about the code you use, you could also input a picture. But you make a feature request for latex, the kernel could perhaps add a fall back to 02c7 to the definition of v.

          – Ulrike Fischer
          Feb 25 at 11:11





          No, newunicodechar doesn't care about the code you use, you could also input a picture. But you make a feature request for latex, the kernel could perhaps add a fall back to 02c7 to the definition of v.

          – Ulrike Fischer
          Feb 25 at 11:11













          Are you sure I can just submit it to the Latex2e github?

          – Paul
          Feb 25 at 11:34





          Are you sure I can just submit it to the Latex2e github?

          – Paul
          Feb 25 at 11:34











          3














          Based on a trick by Egreg, this uses the accent primitive. I chose to simply redefine v.



          documentclass{standalone}
          usepackage{fontspec, newunicodechar}

          usepackage[british]{babel}

          setmainfont[Ligatures=TeX]{Cardo}

          renewcommandv[1]{accentstring"02C7 #1}

          newunicodechar{ǚ}{v{ü}}
          newunicodechar{Ǚ}{v{Ü}}
          newunicodechar{ǎ}{v{a}}
          newunicodechar{Ǎ}{v{A}}
          newunicodechar{ǒ}{v{o}}
          newunicodechar{Ǒ}{v{O}}

          begin{document}

          ǚ Ǚ ǎ Ǎ ǒ Ǒ

          end{document}


          ǚ Ǚ ǎ Ǎ ǒ Ǒ



          I picked Cardo as a common font that contains the caron accent, but not the precomposed ǚ.






          share|improve this answer
























          • I can reproduce the MWE of this solution with Minion Pro. However, for some reason it doesn't work in my actual main file. There is some clash with another package, and I cannot identify (yet) which one it is.

            – Paul
            Feb 25 at 11:23











          • You might to change the documentclass back, if you didn’t. I switched to standalone for the convenience of creating a cropped image. Anyway, just adding the line renewcommandv[1]{accentstring"02C7 #1} ought to work.

            – Davislor
            Feb 25 at 11:32













          • I already checked and your solution definitely works with documentclass[a4paper,12pt,article,oneside]{memoir} Must be something else...

            – Paul
            Feb 25 at 11:34











          • I also removed xunicode? Or maybe it’s related to setmainfont versus babelfont?

            – Davislor
            Feb 25 at 11:42











          • I identified the conflicting package: it's hyperref But I have no idea what causes it

            – Paul
            Feb 25 at 12:27
















          3














          Based on a trick by Egreg, this uses the accent primitive. I chose to simply redefine v.



          documentclass{standalone}
          usepackage{fontspec, newunicodechar}

          usepackage[british]{babel}

          setmainfont[Ligatures=TeX]{Cardo}

          renewcommandv[1]{accentstring"02C7 #1}

          newunicodechar{ǚ}{v{ü}}
          newunicodechar{Ǚ}{v{Ü}}
          newunicodechar{ǎ}{v{a}}
          newunicodechar{Ǎ}{v{A}}
          newunicodechar{ǒ}{v{o}}
          newunicodechar{Ǒ}{v{O}}

          begin{document}

          ǚ Ǚ ǎ Ǎ ǒ Ǒ

          end{document}


          ǚ Ǚ ǎ Ǎ ǒ Ǒ



          I picked Cardo as a common font that contains the caron accent, but not the precomposed ǚ.






          share|improve this answer
























          • I can reproduce the MWE of this solution with Minion Pro. However, for some reason it doesn't work in my actual main file. There is some clash with another package, and I cannot identify (yet) which one it is.

            – Paul
            Feb 25 at 11:23











          • You might to change the documentclass back, if you didn’t. I switched to standalone for the convenience of creating a cropped image. Anyway, just adding the line renewcommandv[1]{accentstring"02C7 #1} ought to work.

            – Davislor
            Feb 25 at 11:32













          • I already checked and your solution definitely works with documentclass[a4paper,12pt,article,oneside]{memoir} Must be something else...

            – Paul
            Feb 25 at 11:34











          • I also removed xunicode? Or maybe it’s related to setmainfont versus babelfont?

            – Davislor
            Feb 25 at 11:42











          • I identified the conflicting package: it's hyperref But I have no idea what causes it

            – Paul
            Feb 25 at 12:27














          3












          3








          3







          Based on a trick by Egreg, this uses the accent primitive. I chose to simply redefine v.



          documentclass{standalone}
          usepackage{fontspec, newunicodechar}

          usepackage[british]{babel}

          setmainfont[Ligatures=TeX]{Cardo}

          renewcommandv[1]{accentstring"02C7 #1}

          newunicodechar{ǚ}{v{ü}}
          newunicodechar{Ǚ}{v{Ü}}
          newunicodechar{ǎ}{v{a}}
          newunicodechar{Ǎ}{v{A}}
          newunicodechar{ǒ}{v{o}}
          newunicodechar{Ǒ}{v{O}}

          begin{document}

          ǚ Ǚ ǎ Ǎ ǒ Ǒ

          end{document}


          ǚ Ǚ ǎ Ǎ ǒ Ǒ



          I picked Cardo as a common font that contains the caron accent, but not the precomposed ǚ.






          share|improve this answer













          Based on a trick by Egreg, this uses the accent primitive. I chose to simply redefine v.



          documentclass{standalone}
          usepackage{fontspec, newunicodechar}

          usepackage[british]{babel}

          setmainfont[Ligatures=TeX]{Cardo}

          renewcommandv[1]{accentstring"02C7 #1}

          newunicodechar{ǚ}{v{ü}}
          newunicodechar{Ǚ}{v{Ü}}
          newunicodechar{ǎ}{v{a}}
          newunicodechar{Ǎ}{v{A}}
          newunicodechar{ǒ}{v{o}}
          newunicodechar{Ǒ}{v{O}}

          begin{document}

          ǚ Ǚ ǎ Ǎ ǒ Ǒ

          end{document}


          ǚ Ǚ ǎ Ǎ ǒ Ǒ



          I picked Cardo as a common font that contains the caron accent, but not the precomposed ǚ.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 25 at 11:06









          DavislorDavislor

          6,5221329




          6,5221329













          • I can reproduce the MWE of this solution with Minion Pro. However, for some reason it doesn't work in my actual main file. There is some clash with another package, and I cannot identify (yet) which one it is.

            – Paul
            Feb 25 at 11:23











          • You might to change the documentclass back, if you didn’t. I switched to standalone for the convenience of creating a cropped image. Anyway, just adding the line renewcommandv[1]{accentstring"02C7 #1} ought to work.

            – Davislor
            Feb 25 at 11:32













          • I already checked and your solution definitely works with documentclass[a4paper,12pt,article,oneside]{memoir} Must be something else...

            – Paul
            Feb 25 at 11:34











          • I also removed xunicode? Or maybe it’s related to setmainfont versus babelfont?

            – Davislor
            Feb 25 at 11:42











          • I identified the conflicting package: it's hyperref But I have no idea what causes it

            – Paul
            Feb 25 at 12:27



















          • I can reproduce the MWE of this solution with Minion Pro. However, for some reason it doesn't work in my actual main file. There is some clash with another package, and I cannot identify (yet) which one it is.

            – Paul
            Feb 25 at 11:23











          • You might to change the documentclass back, if you didn’t. I switched to standalone for the convenience of creating a cropped image. Anyway, just adding the line renewcommandv[1]{accentstring"02C7 #1} ought to work.

            – Davislor
            Feb 25 at 11:32













          • I already checked and your solution definitely works with documentclass[a4paper,12pt,article,oneside]{memoir} Must be something else...

            – Paul
            Feb 25 at 11:34











          • I also removed xunicode? Or maybe it’s related to setmainfont versus babelfont?

            – Davislor
            Feb 25 at 11:42











          • I identified the conflicting package: it's hyperref But I have no idea what causes it

            – Paul
            Feb 25 at 12:27

















          I can reproduce the MWE of this solution with Minion Pro. However, for some reason it doesn't work in my actual main file. There is some clash with another package, and I cannot identify (yet) which one it is.

          – Paul
          Feb 25 at 11:23





          I can reproduce the MWE of this solution with Minion Pro. However, for some reason it doesn't work in my actual main file. There is some clash with another package, and I cannot identify (yet) which one it is.

          – Paul
          Feb 25 at 11:23













          You might to change the documentclass back, if you didn’t. I switched to standalone for the convenience of creating a cropped image. Anyway, just adding the line renewcommandv[1]{accentstring"02C7 #1} ought to work.

          – Davislor
          Feb 25 at 11:32







          You might to change the documentclass back, if you didn’t. I switched to standalone for the convenience of creating a cropped image. Anyway, just adding the line renewcommandv[1]{accentstring"02C7 #1} ought to work.

          – Davislor
          Feb 25 at 11:32















          I already checked and your solution definitely works with documentclass[a4paper,12pt,article,oneside]{memoir} Must be something else...

          – Paul
          Feb 25 at 11:34





          I already checked and your solution definitely works with documentclass[a4paper,12pt,article,oneside]{memoir} Must be something else...

          – Paul
          Feb 25 at 11:34













          I also removed xunicode? Or maybe it’s related to setmainfont versus babelfont?

          – Davislor
          Feb 25 at 11:42





          I also removed xunicode? Or maybe it’s related to setmainfont versus babelfont?

          – Davislor
          Feb 25 at 11:42













          I identified the conflicting package: it's hyperref But I have no idea what causes it

          – Paul
          Feb 25 at 12:27





          I identified the conflicting package: it's hyperref But I have no idea what causes it

          – Paul
          Feb 25 at 12:27


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f476566%2fcaron-accent-va-doesnt-render-without-usepackagexecjk%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          How to send String Array data to Server using php in android

          Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

          Is anime1.com a legal site for watching anime?