Ygthkb

Modern Algebraic Geometry and Analytic Number Theory

Is it really OK to use "because of"?

Why is "rm -r" unable to delete this folder?

Writing dialogues for characters whose first language is not English

Insecure private-key encryption

why typing a variable (or expression) prints the value to stdout?

Minimum Viable Product for RTS game?

How to deal with an underperforming subordinate?

How can I handle players killing my NPC outside of combat?

Can me and my friend spend the summer in Canada (6 weeks) at 16 years old without an adult?

How do dictionaries source attestation?

How long has this character been impersonating a Starfleet Officer?

Word for something that's always reliable, but never the best?

Illustrator to chemdraw

Is there any danger of my neighbor having my wife's signature?

Create linguistic diagram (in TikZ?)

Equivalent of "illegal" for violating civil law

Crack the bank account's password!

Single-row INSERT...SELECT much slower than separate SELECT

Context html export bibliography

What can I do to encourage my players to use their consumables?

Why did Luke use his left hand to shoot?

Identical projects by students at two different colleges: still plagiarism?

What is the draw frequency for 3 consecutive games (same players; amateur level)?

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

Getting (Xe)LaTeX to display accents and characters not included with the fontxeCJK messes with punctuationxeCJK and paragraph indentationThe package zhnumber without xeCJKFontspec/xeCJK AutoFakeBold and copyable Chinese characters in PDFxeCJK doesn't find a font from fileCabin font doesn't render properly apostropheCaron accent in the bibliography causes a microtype errorLetterSpace without usepackage{fontspec}textbf does not work, when use usepackage{xeCJK}Adding spaces in xeCJK for Chinese, Japanese, Korean doesn't work

1

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)

xetex fontspec accents xecjk newunicodechar

share|improve this question

asked 1 hour ago

PaulPaul

11715

add a comment | 

1

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)

xetex fontspec accents xecjk newunicodechar

share|improve this question

asked 1 hour ago

PaulPaul

11715

add a comment | 

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

asked 1 hour ago

PaulPaul

11715

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}

share|improve this question

asked 1 hour ago

PaulPaul

11715

share|improve this question

asked 1 hour ago

PaulPaul

11715

asked 1 hour ago

PaulPaul

11715

asked 1 hour ago

PaulPaul

11715

2 Answers
2

active

oldest

votes

4

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}

share|improve this answer

answered 46 mins ago

Ulrike FischerUlrike Fischer

193k8302684

• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  26 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Are you sure I can just submit it to the Latex2e github?
  
  – Paul
  2 mins ago
  

  
  
  
  

add a comment | 

1

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

answered 30 mins ago

DavislorDavislor

6,4011329

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  13 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  4 mins ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  

add a comment | 

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

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

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

Name

Email

Required, but never shown

4

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}

share|improve this answer

answered 46 mins ago

Ulrike FischerUlrike Fischer

193k8302684

• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  26 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Are you sure I can just submit it to the Latex2e github?
  
  – Paul
  2 mins ago
  

  
  
  
  

add a comment | 

4

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}

share|improve this answer

answered 46 mins ago

Ulrike FischerUlrike Fischer

193k8302684

• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  26 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Are you sure I can just submit it to the Latex2e github?
  
  – Paul
  2 mins ago
  

  
  
  
  

add a comment | 

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}

share|improve this answer

answered 46 mins ago

Ulrike FischerUlrike Fischer

193k8302684

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}

share|improve this answer

answered 46 mins ago

Ulrike FischerUlrike Fischer

193k8302684

answered 46 mins ago

Ulrike FischerUlrike Fischer

193k8302684

answered 46 mins ago

Ulrike FischerUlrike Fischer

193k8302684

1

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

answered 30 mins ago

DavislorDavislor

6,4011329

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  13 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  4 mins ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  

add a comment | 

1

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

answered 30 mins ago

DavislorDavislor

6,4011329

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  13 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  4 mins ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

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

  
  
  
  

add a comment | 

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

answered 30 mins ago

DavislorDavislor

6,4011329

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}

share|improve this answer

answered 30 mins ago

DavislorDavislor

6,4011329

answered 30 mins ago

DavislorDavislor

6,4011329

answered 30 mins ago

DavislorDavislor

6,4011329