Problem with dtx file after LaTeX kernel upgrade (2018/04/01)DTX file generates empty fileCan I convert a dtx...
How is it possible to have an ability score that is less than 3?
DOS, create pipe for stdin/stdout of command.com(or 4dos.com) in C or Batch?
Email Account under attack (really) - anything I can do?
is there really no realistic way for skeleton monster to move around without magic?
Have astronauts in space suits ever taken selfies? If so, how?
Why are 150k or 200k jobs considered good when there are 300k+ births a month?
What do you call a Matrix-like slowdown and camera movement effect?
Accidentally leaked the solution to an assignment, what to do now? (I'm the prof)
Why does Kotter return in Welcome Back Kotter?
Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?
Risk of getting Chronic Wasting Disease (CWD) in the United States?
I’m planning on buying a laser printer but concerned about the life cycle of toner in the machine
Languages that we cannot (dis)prove to be Context-Free
What is the difference between 元 (圓), 幣, and 金?
How do you know if an analog film camera is still working?
How old can references or sources in a thesis be?
Modeling an IPv4 Address
What are these boxed doors outside store fronts in New York?
Is the month field really deprecated?
Basic combinations logic doubt in probability
How can bays and straits be determined in a procedurally generated map?
What are the differences between the usage of 'it' and 'they'?
Animated Series: Alien black spider robot crashes on Earth
How to say job offer in Mandarin/Cantonese?
Problem with dtx file after LaTeX kernel upgrade (2018/04/01)
DTX file generates empty fileCan I convert a dtx file to tex filegeneration of sty file from dtx failsProblem with dtx code: rowcolors unknowndtx file and historyWhat exactly happens when LaTeX runs on a dtx file?README file creation from a dtx fileIs it possible to make comments in dtx file?dirtree clashes with dtx-fileDTX: Avoid preamble for non-latex files?
Today, the generation of one of my dtx files stopped with the error:
! Undefined control sequence.
UseTextAccent ...up @firstofone let @curr@enc
cf@encoding @use@text@en...
As I have not changed the files for more than two months now, but updated my MiKTeX last week (and listened carefully to @Ulrike Fischer reporting on kernel changes at the last DANTE meeting), I gladly found out rather quickly, that the new LaTeX kernel (2018/04/01) is responsible for that.
Using pdflatex 'UseRawInputEncoding input{FILENAME.dtx}' as stated in the LaTeX news document, everything runs smoothly.
I then started preparing a MWE, which led to newunicodechar from the same called package causing the problem:
% iffalse meta-comment
%<*internal>
iffalse
%</internal>
%<*internal>
fi
defnameofplainTeX{plain}
ifxfmtnamenameofplainTeXelse
expandafterbegingroup
fi
%</internal>
%<*install>
input docstrip.tex
keepsilent
askforoverwritefalse
generate{
file{jobname.cls}{from{jobname.dtx}{class}}
}
%</install>
%<install>endbatchfile
%<*internal>
generate{
file{jobname.ins}{from{jobname.dtx}{install}}
}
ifxfmtnamenameofplainTeX
expandafterendbatchfile
else
expandafterendgroup
fi
%</internal>
% fi
%
% iffalse
%<*driver>
ProvidesFile{testclass.dtx}
%</driver>
%<class>NeedsTeXFormat{LaTeX2e}[1999/12/01]
%<class>ProvidesClass{testclass}
%<*class>
[2018/04/16 v1.0 A LaTeX class]
%</class>
%<*driver>
documentclass{ltxdoc}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[ngerman]{babel}
EnableCrossrefs
CodelineIndex
RecordChanges
begin{document}
DocInput{jobname.dtx}
end{document}
%</driver>
% fi
%
% CheckSum{0}
%
% CharacterTable
% {Upper-case ABCDEFGHIJKLMNOPQRSTUVWXYZ
% Lower-case abcdefghijklmnopqrstuvwxyz
% Digits 123456789
% Exclamation ! Double quote " Hash (number) #
% Dollar $ Percent % Ampersand &
% Acute accent ' Left paren ( Right paren )
% Asterisk * Plus + Comma ,
% Minus - Point . Solidus /
% Colon : Semicolon ; Less than <
% Equals = Greater than > Question mark ?
% Commercial at @ Left bracket [ Backslash \
% Right bracket ] Circumflex ^ Underscore _
% Grave accent ` Left brace { Vertical bar |
% Right brace } Tilde ~}
% GetFileInfo{jobname.dtx}
% DoNotIndex{newcommand,newenvironment}
%
% title{A test class}
% author{Martin Sievers}
%
% maketitle
%
% StopEventually{^^A
% PrintChanges
% }
%
% section{Implementation}
% begin{macrocode}
%<*class>
% end{macrocode}
% begin{macrocode}
LoadClass{minimal}
% end{macrocode}
% begin{macrocode}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[english]{babel}
RequirePackage{newunicodechar}
newunicodechar{⸗}{hyphen}
% end{macrocode}
% begin{macrocode}
%</class>
% end{macrocode}
% Finale
endinput
However, putting everything into a simple LaTeX file does not result in the same error. So, there must be more about it ...
Is this a foreseeable problem caused by the change to UTF8 as the new standard encoding of files? The dtx file is encoded as UTF8 and as you can see there is always an inputenc entry using the utf8 option as well.
input-encodings latex-base dtx
|
show 3 more comments
Today, the generation of one of my dtx files stopped with the error:
! Undefined control sequence.
UseTextAccent ...up @firstofone let @curr@enc
cf@encoding @use@text@en...
As I have not changed the files for more than two months now, but updated my MiKTeX last week (and listened carefully to @Ulrike Fischer reporting on kernel changes at the last DANTE meeting), I gladly found out rather quickly, that the new LaTeX kernel (2018/04/01) is responsible for that.
Using pdflatex 'UseRawInputEncoding input{FILENAME.dtx}' as stated in the LaTeX news document, everything runs smoothly.
I then started preparing a MWE, which led to newunicodechar from the same called package causing the problem:
% iffalse meta-comment
%<*internal>
iffalse
%</internal>
%<*internal>
fi
defnameofplainTeX{plain}
ifxfmtnamenameofplainTeXelse
expandafterbegingroup
fi
%</internal>
%<*install>
input docstrip.tex
keepsilent
askforoverwritefalse
generate{
file{jobname.cls}{from{jobname.dtx}{class}}
}
%</install>
%<install>endbatchfile
%<*internal>
generate{
file{jobname.ins}{from{jobname.dtx}{install}}
}
ifxfmtnamenameofplainTeX
expandafterendbatchfile
else
expandafterendgroup
fi
%</internal>
% fi
%
% iffalse
%<*driver>
ProvidesFile{testclass.dtx}
%</driver>
%<class>NeedsTeXFormat{LaTeX2e}[1999/12/01]
%<class>ProvidesClass{testclass}
%<*class>
[2018/04/16 v1.0 A LaTeX class]
%</class>
%<*driver>
documentclass{ltxdoc}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[ngerman]{babel}
EnableCrossrefs
CodelineIndex
RecordChanges
begin{document}
DocInput{jobname.dtx}
end{document}
%</driver>
% fi
%
% CheckSum{0}
%
% CharacterTable
% {Upper-case ABCDEFGHIJKLMNOPQRSTUVWXYZ
% Lower-case abcdefghijklmnopqrstuvwxyz
% Digits 123456789
% Exclamation ! Double quote " Hash (number) #
% Dollar $ Percent % Ampersand &
% Acute accent ' Left paren ( Right paren )
% Asterisk * Plus + Comma ,
% Minus - Point . Solidus /
% Colon : Semicolon ; Less than <
% Equals = Greater than > Question mark ?
% Commercial at @ Left bracket [ Backslash \
% Right bracket ] Circumflex ^ Underscore _
% Grave accent ` Left brace { Vertical bar |
% Right brace } Tilde ~}
% GetFileInfo{jobname.dtx}
% DoNotIndex{newcommand,newenvironment}
%
% title{A test class}
% author{Martin Sievers}
%
% maketitle
%
% StopEventually{^^A
% PrintChanges
% }
%
% section{Implementation}
% begin{macrocode}
%<*class>
% end{macrocode}
% begin{macrocode}
LoadClass{minimal}
% end{macrocode}
% begin{macrocode}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[english]{babel}
RequirePackage{newunicodechar}
newunicodechar{⸗}{hyphen}
% end{macrocode}
% begin{macrocode}
%</class>
% end{macrocode}
% Finale
endinput
However, putting everything into a simple LaTeX file does not result in the same error. So, there must be more about it ...
Is this a foreseeable problem caused by the change to UTF8 as the new standard encoding of files? The dtx file is encoded as UTF8 and as you can see there is always an inputenc entry using the utf8 option as well.
input-encodings latex-base dtx
2
There was a commit on the LaTeX2e git (github.com/latex3/latex2e/commit/…) that changed something for docstrip following github.com/latex3/latex2e/issues/34. I don't think that version has been released, the changes certainly have not made it to my MikTeX yet (updated this morning).
– moewe
Apr 16 '18 at 13:20
github.com/latex3/latex2e/issues/34 Also mentions puttingUseRawInputEncodingat the top of the.insfile to solve this. For me that generates an unknown control sequence, though when running the.dtxwith pdfTeX. And I get Unicode character not set up for use when running with pdfLaTeX.
– moewe
Apr 16 '18 at 13:30
@moewe That's the answer ('the team are still covering a few cases'): do you want to post something?
– Joseph Wright♦
Apr 16 '18 at 13:57
2
@JosephWright Well, if someone who actually knows what is going on can give an answer with a workaround that works out of the box in this case, that is probably preferable to my answer just linking to the issue on GitHub.
– moewe
Apr 16 '18 at 14:08
@JosephWright Should this problem be solved in PL4? Part of it seems to be resolved, but I still getUnicode character ⸗ (U+2E17) not set up for use with LaTeX.despite/in thenewunicodechar.
– moewe
May 5 '18 at 14:15
|
show 3 more comments
Today, the generation of one of my dtx files stopped with the error:
! Undefined control sequence.
UseTextAccent ...up @firstofone let @curr@enc
cf@encoding @use@text@en...
As I have not changed the files for more than two months now, but updated my MiKTeX last week (and listened carefully to @Ulrike Fischer reporting on kernel changes at the last DANTE meeting), I gladly found out rather quickly, that the new LaTeX kernel (2018/04/01) is responsible for that.
Using pdflatex 'UseRawInputEncoding input{FILENAME.dtx}' as stated in the LaTeX news document, everything runs smoothly.
I then started preparing a MWE, which led to newunicodechar from the same called package causing the problem:
% iffalse meta-comment
%<*internal>
iffalse
%</internal>
%<*internal>
fi
defnameofplainTeX{plain}
ifxfmtnamenameofplainTeXelse
expandafterbegingroup
fi
%</internal>
%<*install>
input docstrip.tex
keepsilent
askforoverwritefalse
generate{
file{jobname.cls}{from{jobname.dtx}{class}}
}
%</install>
%<install>endbatchfile
%<*internal>
generate{
file{jobname.ins}{from{jobname.dtx}{install}}
}
ifxfmtnamenameofplainTeX
expandafterendbatchfile
else
expandafterendgroup
fi
%</internal>
% fi
%
% iffalse
%<*driver>
ProvidesFile{testclass.dtx}
%</driver>
%<class>NeedsTeXFormat{LaTeX2e}[1999/12/01]
%<class>ProvidesClass{testclass}
%<*class>
[2018/04/16 v1.0 A LaTeX class]
%</class>
%<*driver>
documentclass{ltxdoc}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[ngerman]{babel}
EnableCrossrefs
CodelineIndex
RecordChanges
begin{document}
DocInput{jobname.dtx}
end{document}
%</driver>
% fi
%
% CheckSum{0}
%
% CharacterTable
% {Upper-case ABCDEFGHIJKLMNOPQRSTUVWXYZ
% Lower-case abcdefghijklmnopqrstuvwxyz
% Digits 123456789
% Exclamation ! Double quote " Hash (number) #
% Dollar $ Percent % Ampersand &
% Acute accent ' Left paren ( Right paren )
% Asterisk * Plus + Comma ,
% Minus - Point . Solidus /
% Colon : Semicolon ; Less than <
% Equals = Greater than > Question mark ?
% Commercial at @ Left bracket [ Backslash \
% Right bracket ] Circumflex ^ Underscore _
% Grave accent ` Left brace { Vertical bar |
% Right brace } Tilde ~}
% GetFileInfo{jobname.dtx}
% DoNotIndex{newcommand,newenvironment}
%
% title{A test class}
% author{Martin Sievers}
%
% maketitle
%
% StopEventually{^^A
% PrintChanges
% }
%
% section{Implementation}
% begin{macrocode}
%<*class>
% end{macrocode}
% begin{macrocode}
LoadClass{minimal}
% end{macrocode}
% begin{macrocode}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[english]{babel}
RequirePackage{newunicodechar}
newunicodechar{⸗}{hyphen}
% end{macrocode}
% begin{macrocode}
%</class>
% end{macrocode}
% Finale
endinput
However, putting everything into a simple LaTeX file does not result in the same error. So, there must be more about it ...
Is this a foreseeable problem caused by the change to UTF8 as the new standard encoding of files? The dtx file is encoded as UTF8 and as you can see there is always an inputenc entry using the utf8 option as well.
input-encodings latex-base dtx
Today, the generation of one of my dtx files stopped with the error:
! Undefined control sequence.
UseTextAccent ...up @firstofone let @curr@enc
cf@encoding @use@text@en...
As I have not changed the files for more than two months now, but updated my MiKTeX last week (and listened carefully to @Ulrike Fischer reporting on kernel changes at the last DANTE meeting), I gladly found out rather quickly, that the new LaTeX kernel (2018/04/01) is responsible for that.
Using pdflatex 'UseRawInputEncoding input{FILENAME.dtx}' as stated in the LaTeX news document, everything runs smoothly.
I then started preparing a MWE, which led to newunicodechar from the same called package causing the problem:
% iffalse meta-comment
%<*internal>
iffalse
%</internal>
%<*internal>
fi
defnameofplainTeX{plain}
ifxfmtnamenameofplainTeXelse
expandafterbegingroup
fi
%</internal>
%<*install>
input docstrip.tex
keepsilent
askforoverwritefalse
generate{
file{jobname.cls}{from{jobname.dtx}{class}}
}
%</install>
%<install>endbatchfile
%<*internal>
generate{
file{jobname.ins}{from{jobname.dtx}{install}}
}
ifxfmtnamenameofplainTeX
expandafterendbatchfile
else
expandafterendgroup
fi
%</internal>
% fi
%
% iffalse
%<*driver>
ProvidesFile{testclass.dtx}
%</driver>
%<class>NeedsTeXFormat{LaTeX2e}[1999/12/01]
%<class>ProvidesClass{testclass}
%<*class>
[2018/04/16 v1.0 A LaTeX class]
%</class>
%<*driver>
documentclass{ltxdoc}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[ngerman]{babel}
EnableCrossrefs
CodelineIndex
RecordChanges
begin{document}
DocInput{jobname.dtx}
end{document}
%</driver>
% fi
%
% CheckSum{0}
%
% CharacterTable
% {Upper-case ABCDEFGHIJKLMNOPQRSTUVWXYZ
% Lower-case abcdefghijklmnopqrstuvwxyz
% Digits 123456789
% Exclamation ! Double quote " Hash (number) #
% Dollar $ Percent % Ampersand &
% Acute accent ' Left paren ( Right paren )
% Asterisk * Plus + Comma ,
% Minus - Point . Solidus /
% Colon : Semicolon ; Less than <
% Equals = Greater than > Question mark ?
% Commercial at @ Left bracket [ Backslash \
% Right bracket ] Circumflex ^ Underscore _
% Grave accent ` Left brace { Vertical bar |
% Right brace } Tilde ~}
% GetFileInfo{jobname.dtx}
% DoNotIndex{newcommand,newenvironment}
%
% title{A test class}
% author{Martin Sievers}
%
% maketitle
%
% StopEventually{^^A
% PrintChanges
% }
%
% section{Implementation}
% begin{macrocode}
%<*class>
% end{macrocode}
% begin{macrocode}
LoadClass{minimal}
% end{macrocode}
% begin{macrocode}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[english]{babel}
RequirePackage{newunicodechar}
newunicodechar{⸗}{hyphen}
% end{macrocode}
% begin{macrocode}
%</class>
% end{macrocode}
% Finale
endinput
However, putting everything into a simple LaTeX file does not result in the same error. So, there must be more about it ...
Is this a foreseeable problem caused by the change to UTF8 as the new standard encoding of files? The dtx file is encoded as UTF8 and as you can see there is always an inputenc entry using the utf8 option as well.
input-encodings latex-base dtx
input-encodings latex-base dtx
edited Apr 19 '18 at 5:31
TeXnician
25.9k63491
25.9k63491
asked Apr 16 '18 at 13:09
MartinMartin
61249
61249
2
There was a commit on the LaTeX2e git (github.com/latex3/latex2e/commit/…) that changed something for docstrip following github.com/latex3/latex2e/issues/34. I don't think that version has been released, the changes certainly have not made it to my MikTeX yet (updated this morning).
– moewe
Apr 16 '18 at 13:20
github.com/latex3/latex2e/issues/34 Also mentions puttingUseRawInputEncodingat the top of the.insfile to solve this. For me that generates an unknown control sequence, though when running the.dtxwith pdfTeX. And I get Unicode character not set up for use when running with pdfLaTeX.
– moewe
Apr 16 '18 at 13:30
@moewe That's the answer ('the team are still covering a few cases'): do you want to post something?
– Joseph Wright♦
Apr 16 '18 at 13:57
2
@JosephWright Well, if someone who actually knows what is going on can give an answer with a workaround that works out of the box in this case, that is probably preferable to my answer just linking to the issue on GitHub.
– moewe
Apr 16 '18 at 14:08
@JosephWright Should this problem be solved in PL4? Part of it seems to be resolved, but I still getUnicode character ⸗ (U+2E17) not set up for use with LaTeX.despite/in thenewunicodechar.
– moewe
May 5 '18 at 14:15
|
show 3 more comments
2
There was a commit on the LaTeX2e git (github.com/latex3/latex2e/commit/…) that changed something for docstrip following github.com/latex3/latex2e/issues/34. I don't think that version has been released, the changes certainly have not made it to my MikTeX yet (updated this morning).
– moewe
Apr 16 '18 at 13:20
github.com/latex3/latex2e/issues/34 Also mentions puttingUseRawInputEncodingat the top of the.insfile to solve this. For me that generates an unknown control sequence, though when running the.dtxwith pdfTeX. And I get Unicode character not set up for use when running with pdfLaTeX.
– moewe
Apr 16 '18 at 13:30
@moewe That's the answer ('the team are still covering a few cases'): do you want to post something?
– Joseph Wright♦
Apr 16 '18 at 13:57
2
@JosephWright Well, if someone who actually knows what is going on can give an answer with a workaround that works out of the box in this case, that is probably preferable to my answer just linking to the issue on GitHub.
– moewe
Apr 16 '18 at 14:08
@JosephWright Should this problem be solved in PL4? Part of it seems to be resolved, but I still getUnicode character ⸗ (U+2E17) not set up for use with LaTeX.despite/in thenewunicodechar.
– moewe
May 5 '18 at 14:15
2
2
There was a commit on the LaTeX2e git (github.com/latex3/latex2e/commit/…) that changed something for docstrip following github.com/latex3/latex2e/issues/34. I don't think that version has been released, the changes certainly have not made it to my MikTeX yet (updated this morning).
– moewe
Apr 16 '18 at 13:20
There was a commit on the LaTeX2e git (github.com/latex3/latex2e/commit/…) that changed something for docstrip following github.com/latex3/latex2e/issues/34. I don't think that version has been released, the changes certainly have not made it to my MikTeX yet (updated this morning).
– moewe
Apr 16 '18 at 13:20
github.com/latex3/latex2e/issues/34 Also mentions putting
UseRawInputEncoding at the top of the .ins file to solve this. For me that generates an unknown control sequence, though when running the .dtx with pdfTeX. And I get Unicode character not set up for use when running with pdfLaTeX.– moewe
Apr 16 '18 at 13:30
github.com/latex3/latex2e/issues/34 Also mentions putting
UseRawInputEncoding at the top of the .ins file to solve this. For me that generates an unknown control sequence, though when running the .dtx with pdfTeX. And I get Unicode character not set up for use when running with pdfLaTeX.– moewe
Apr 16 '18 at 13:30
@moewe That's the answer ('the team are still covering a few cases'): do you want to post something?
– Joseph Wright♦
Apr 16 '18 at 13:57
@moewe That's the answer ('the team are still covering a few cases'): do you want to post something?
– Joseph Wright♦
Apr 16 '18 at 13:57
2
2
@JosephWright Well, if someone who actually knows what is going on can give an answer with a workaround that works out of the box in this case, that is probably preferable to my answer just linking to the issue on GitHub.
– moewe
Apr 16 '18 at 14:08
@JosephWright Well, if someone who actually knows what is going on can give an answer with a workaround that works out of the box in this case, that is probably preferable to my answer just linking to the issue on GitHub.
– moewe
Apr 16 '18 at 14:08
@JosephWright Should this problem be solved in PL4? Part of it seems to be resolved, but I still get
Unicode character ⸗ (U+2E17) not set up for use with LaTeX. despite/in the newunicodechar.– moewe
May 5 '18 at 14:15
@JosephWright Should this problem be solved in PL4? Part of it seems to be resolved, but I still get
Unicode character ⸗ (U+2E17) not set up for use with LaTeX. despite/in the newunicodechar.– moewe
May 5 '18 at 14:15
|
show 3 more comments
1 Answer
1
active
oldest
votes
With current (2018,2019) releases
The posted code produces the error
! Package inputenc Error: Unicode char ⸗ (U+2E17)
(inputenc) not set up for use with LaTeX.
The problem is that the newunicodechar package is loaded and used to declare this character in the generated class file, but the typeset documentation is not using this class and so latex can not typeset this line:
newunicodechar{⸗}{hyphen}
You can declare a setting for this character in the typeset document, the standard fonts don't really have a suitable character so I just used - here.
This is as posted in the question, with the addition of
DeclareUnicodeCharacter{2E17}{-}
% iffalse meta-comment
%<*internal>
iffalse
%</internal>
%<*internal>
fi
defnameofplainTeX{plain}
ifxfmtnamenameofplainTeXelse
expandafterbegingroup
fi
%</internal>
%<*install>
input docstrip.tex
keepsilent
askforoverwritefalse
generate{
file{jobname.cls}{from{jobname.dtx}{class}}
}
%</install>
%<install>endbatchfile
%<*internal>
generate{
file{jobname.ins}{from{jobname.dtx}{install}}
}
ifxfmtnamenameofplainTeX
expandafterendbatchfile
else
expandafterendgroup
fi
%</internal>
% fi
%
% iffalse
%<*driver>
ProvidesFile{testclass.dtx}
%</driver>
%<class>NeedsTeXFormat{LaTeX2e}[1999/12/01]
%<class>ProvidesClass{testclass}
%<*class>
[2018/04/16 v1.0 A LaTeX class]
%</class>
%<*driver>
documentclass{ltxdoc}
RequirePackage[utf8]{inputenc}
DeclareUnicodeCharacter{2E17}{-}
RequirePackage[T1]{fontenc}
RequirePackage[ngerman]{babel}
EnableCrossrefs
CodelineIndex
RecordChanges
begin{document}
DocInput{jobname.dtx}
end{document}
%</driver>
% fi
%
% CheckSum{0}
%
% CharacterTable
% {Upper-case ABCDEFGHIJKLMNOPQRSTUVWXYZ
% Lower-case abcdefghijklmnopqrstuvwxyz
% Digits 123456789
% Exclamation ! Double quote " Hash (number) #
% Dollar $ Percent % Ampersand &
% Acute accent ' Left paren ( Right paren )
% Asterisk * Plus + Comma ,
% Minus - Point . Solidus /
% Colon : Semicolon ; Less than <
% Equals = Greater than > Question mark ?
% Commercial at @ Left bracket [ Backslash \
% Right bracket ] Circumflex ^ Underscore _
% Grave accent ` Left brace { Vertical bar |
% Right brace } Tilde ~}
% GetFileInfo{jobname.dtx}
% DoNotIndex{newcommand,newenvironment}
%
% title{A test class}
% author{Martin Sievers}
%
% maketitle
%
% StopEventually{^^A
% PrintChanges
% }
%
% section{Implementation}
% begin{macrocode}
%<*class>
% end{macrocode}
% begin{macrocode}
LoadClass{minimal}
% end{macrocode}
% begin{macrocode}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[english]{babel}
RequirePackage{newunicodechar}
newunicodechar{⸗}{hyphen}
% end{macrocode}
% begin{macrocode}
%</class>
% end{macrocode}
% Finale
endinput
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
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f426819%2fproblem-with-dtx-file-after-latex-kernel-upgrade-2018-04-01%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
With current (2018,2019) releases
The posted code produces the error
! Package inputenc Error: Unicode char ⸗ (U+2E17)
(inputenc) not set up for use with LaTeX.
The problem is that the newunicodechar package is loaded and used to declare this character in the generated class file, but the typeset documentation is not using this class and so latex can not typeset this line:
newunicodechar{⸗}{hyphen}
You can declare a setting for this character in the typeset document, the standard fonts don't really have a suitable character so I just used - here.
This is as posted in the question, with the addition of
DeclareUnicodeCharacter{2E17}{-}
% iffalse meta-comment
%<*internal>
iffalse
%</internal>
%<*internal>
fi
defnameofplainTeX{plain}
ifxfmtnamenameofplainTeXelse
expandafterbegingroup
fi
%</internal>
%<*install>
input docstrip.tex
keepsilent
askforoverwritefalse
generate{
file{jobname.cls}{from{jobname.dtx}{class}}
}
%</install>
%<install>endbatchfile
%<*internal>
generate{
file{jobname.ins}{from{jobname.dtx}{install}}
}
ifxfmtnamenameofplainTeX
expandafterendbatchfile
else
expandafterendgroup
fi
%</internal>
% fi
%
% iffalse
%<*driver>
ProvidesFile{testclass.dtx}
%</driver>
%<class>NeedsTeXFormat{LaTeX2e}[1999/12/01]
%<class>ProvidesClass{testclass}
%<*class>
[2018/04/16 v1.0 A LaTeX class]
%</class>
%<*driver>
documentclass{ltxdoc}
RequirePackage[utf8]{inputenc}
DeclareUnicodeCharacter{2E17}{-}
RequirePackage[T1]{fontenc}
RequirePackage[ngerman]{babel}
EnableCrossrefs
CodelineIndex
RecordChanges
begin{document}
DocInput{jobname.dtx}
end{document}
%</driver>
% fi
%
% CheckSum{0}
%
% CharacterTable
% {Upper-case ABCDEFGHIJKLMNOPQRSTUVWXYZ
% Lower-case abcdefghijklmnopqrstuvwxyz
% Digits 123456789
% Exclamation ! Double quote " Hash (number) #
% Dollar $ Percent % Ampersand &
% Acute accent ' Left paren ( Right paren )
% Asterisk * Plus + Comma ,
% Minus - Point . Solidus /
% Colon : Semicolon ; Less than <
% Equals = Greater than > Question mark ?
% Commercial at @ Left bracket [ Backslash \
% Right bracket ] Circumflex ^ Underscore _
% Grave accent ` Left brace { Vertical bar |
% Right brace } Tilde ~}
% GetFileInfo{jobname.dtx}
% DoNotIndex{newcommand,newenvironment}
%
% title{A test class}
% author{Martin Sievers}
%
% maketitle
%
% StopEventually{^^A
% PrintChanges
% }
%
% section{Implementation}
% begin{macrocode}
%<*class>
% end{macrocode}
% begin{macrocode}
LoadClass{minimal}
% end{macrocode}
% begin{macrocode}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[english]{babel}
RequirePackage{newunicodechar}
newunicodechar{⸗}{hyphen}
% end{macrocode}
% begin{macrocode}
%</class>
% end{macrocode}
% Finale
endinput
add a comment |
With current (2018,2019) releases
The posted code produces the error
! Package inputenc Error: Unicode char ⸗ (U+2E17)
(inputenc) not set up for use with LaTeX.
The problem is that the newunicodechar package is loaded and used to declare this character in the generated class file, but the typeset documentation is not using this class and so latex can not typeset this line:
newunicodechar{⸗}{hyphen}
You can declare a setting for this character in the typeset document, the standard fonts don't really have a suitable character so I just used - here.
This is as posted in the question, with the addition of
DeclareUnicodeCharacter{2E17}{-}
% iffalse meta-comment
%<*internal>
iffalse
%</internal>
%<*internal>
fi
defnameofplainTeX{plain}
ifxfmtnamenameofplainTeXelse
expandafterbegingroup
fi
%</internal>
%<*install>
input docstrip.tex
keepsilent
askforoverwritefalse
generate{
file{jobname.cls}{from{jobname.dtx}{class}}
}
%</install>
%<install>endbatchfile
%<*internal>
generate{
file{jobname.ins}{from{jobname.dtx}{install}}
}
ifxfmtnamenameofplainTeX
expandafterendbatchfile
else
expandafterendgroup
fi
%</internal>
% fi
%
% iffalse
%<*driver>
ProvidesFile{testclass.dtx}
%</driver>
%<class>NeedsTeXFormat{LaTeX2e}[1999/12/01]
%<class>ProvidesClass{testclass}
%<*class>
[2018/04/16 v1.0 A LaTeX class]
%</class>
%<*driver>
documentclass{ltxdoc}
RequirePackage[utf8]{inputenc}
DeclareUnicodeCharacter{2E17}{-}
RequirePackage[T1]{fontenc}
RequirePackage[ngerman]{babel}
EnableCrossrefs
CodelineIndex
RecordChanges
begin{document}
DocInput{jobname.dtx}
end{document}
%</driver>
% fi
%
% CheckSum{0}
%
% CharacterTable
% {Upper-case ABCDEFGHIJKLMNOPQRSTUVWXYZ
% Lower-case abcdefghijklmnopqrstuvwxyz
% Digits 123456789
% Exclamation ! Double quote " Hash (number) #
% Dollar $ Percent % Ampersand &
% Acute accent ' Left paren ( Right paren )
% Asterisk * Plus + Comma ,
% Minus - Point . Solidus /
% Colon : Semicolon ; Less than <
% Equals = Greater than > Question mark ?
% Commercial at @ Left bracket [ Backslash \
% Right bracket ] Circumflex ^ Underscore _
% Grave accent ` Left brace { Vertical bar |
% Right brace } Tilde ~}
% GetFileInfo{jobname.dtx}
% DoNotIndex{newcommand,newenvironment}
%
% title{A test class}
% author{Martin Sievers}
%
% maketitle
%
% StopEventually{^^A
% PrintChanges
% }
%
% section{Implementation}
% begin{macrocode}
%<*class>
% end{macrocode}
% begin{macrocode}
LoadClass{minimal}
% end{macrocode}
% begin{macrocode}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[english]{babel}
RequirePackage{newunicodechar}
newunicodechar{⸗}{hyphen}
% end{macrocode}
% begin{macrocode}
%</class>
% end{macrocode}
% Finale
endinput
add a comment |
With current (2018,2019) releases
The posted code produces the error
! Package inputenc Error: Unicode char ⸗ (U+2E17)
(inputenc) not set up for use with LaTeX.
The problem is that the newunicodechar package is loaded and used to declare this character in the generated class file, but the typeset documentation is not using this class and so latex can not typeset this line:
newunicodechar{⸗}{hyphen}
You can declare a setting for this character in the typeset document, the standard fonts don't really have a suitable character so I just used - here.
This is as posted in the question, with the addition of
DeclareUnicodeCharacter{2E17}{-}
% iffalse meta-comment
%<*internal>
iffalse
%</internal>
%<*internal>
fi
defnameofplainTeX{plain}
ifxfmtnamenameofplainTeXelse
expandafterbegingroup
fi
%</internal>
%<*install>
input docstrip.tex
keepsilent
askforoverwritefalse
generate{
file{jobname.cls}{from{jobname.dtx}{class}}
}
%</install>
%<install>endbatchfile
%<*internal>
generate{
file{jobname.ins}{from{jobname.dtx}{install}}
}
ifxfmtnamenameofplainTeX
expandafterendbatchfile
else
expandafterendgroup
fi
%</internal>
% fi
%
% iffalse
%<*driver>
ProvidesFile{testclass.dtx}
%</driver>
%<class>NeedsTeXFormat{LaTeX2e}[1999/12/01]
%<class>ProvidesClass{testclass}
%<*class>
[2018/04/16 v1.0 A LaTeX class]
%</class>
%<*driver>
documentclass{ltxdoc}
RequirePackage[utf8]{inputenc}
DeclareUnicodeCharacter{2E17}{-}
RequirePackage[T1]{fontenc}
RequirePackage[ngerman]{babel}
EnableCrossrefs
CodelineIndex
RecordChanges
begin{document}
DocInput{jobname.dtx}
end{document}
%</driver>
% fi
%
% CheckSum{0}
%
% CharacterTable
% {Upper-case ABCDEFGHIJKLMNOPQRSTUVWXYZ
% Lower-case abcdefghijklmnopqrstuvwxyz
% Digits 123456789
% Exclamation ! Double quote " Hash (number) #
% Dollar $ Percent % Ampersand &
% Acute accent ' Left paren ( Right paren )
% Asterisk * Plus + Comma ,
% Minus - Point . Solidus /
% Colon : Semicolon ; Less than <
% Equals = Greater than > Question mark ?
% Commercial at @ Left bracket [ Backslash \
% Right bracket ] Circumflex ^ Underscore _
% Grave accent ` Left brace { Vertical bar |
% Right brace } Tilde ~}
% GetFileInfo{jobname.dtx}
% DoNotIndex{newcommand,newenvironment}
%
% title{A test class}
% author{Martin Sievers}
%
% maketitle
%
% StopEventually{^^A
% PrintChanges
% }
%
% section{Implementation}
% begin{macrocode}
%<*class>
% end{macrocode}
% begin{macrocode}
LoadClass{minimal}
% end{macrocode}
% begin{macrocode}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[english]{babel}
RequirePackage{newunicodechar}
newunicodechar{⸗}{hyphen}
% end{macrocode}
% begin{macrocode}
%</class>
% end{macrocode}
% Finale
endinput
With current (2018,2019) releases
The posted code produces the error
! Package inputenc Error: Unicode char ⸗ (U+2E17)
(inputenc) not set up for use with LaTeX.
The problem is that the newunicodechar package is loaded and used to declare this character in the generated class file, but the typeset documentation is not using this class and so latex can not typeset this line:
newunicodechar{⸗}{hyphen}
You can declare a setting for this character in the typeset document, the standard fonts don't really have a suitable character so I just used - here.
This is as posted in the question, with the addition of
DeclareUnicodeCharacter{2E17}{-}
% iffalse meta-comment
%<*internal>
iffalse
%</internal>
%<*internal>
fi
defnameofplainTeX{plain}
ifxfmtnamenameofplainTeXelse
expandafterbegingroup
fi
%</internal>
%<*install>
input docstrip.tex
keepsilent
askforoverwritefalse
generate{
file{jobname.cls}{from{jobname.dtx}{class}}
}
%</install>
%<install>endbatchfile
%<*internal>
generate{
file{jobname.ins}{from{jobname.dtx}{install}}
}
ifxfmtnamenameofplainTeX
expandafterendbatchfile
else
expandafterendgroup
fi
%</internal>
% fi
%
% iffalse
%<*driver>
ProvidesFile{testclass.dtx}
%</driver>
%<class>NeedsTeXFormat{LaTeX2e}[1999/12/01]
%<class>ProvidesClass{testclass}
%<*class>
[2018/04/16 v1.0 A LaTeX class]
%</class>
%<*driver>
documentclass{ltxdoc}
RequirePackage[utf8]{inputenc}
DeclareUnicodeCharacter{2E17}{-}
RequirePackage[T1]{fontenc}
RequirePackage[ngerman]{babel}
EnableCrossrefs
CodelineIndex
RecordChanges
begin{document}
DocInput{jobname.dtx}
end{document}
%</driver>
% fi
%
% CheckSum{0}
%
% CharacterTable
% {Upper-case ABCDEFGHIJKLMNOPQRSTUVWXYZ
% Lower-case abcdefghijklmnopqrstuvwxyz
% Digits 123456789
% Exclamation ! Double quote " Hash (number) #
% Dollar $ Percent % Ampersand &
% Acute accent ' Left paren ( Right paren )
% Asterisk * Plus + Comma ,
% Minus - Point . Solidus /
% Colon : Semicolon ; Less than <
% Equals = Greater than > Question mark ?
% Commercial at @ Left bracket [ Backslash \
% Right bracket ] Circumflex ^ Underscore _
% Grave accent ` Left brace { Vertical bar |
% Right brace } Tilde ~}
% GetFileInfo{jobname.dtx}
% DoNotIndex{newcommand,newenvironment}
%
% title{A test class}
% author{Martin Sievers}
%
% maketitle
%
% StopEventually{^^A
% PrintChanges
% }
%
% section{Implementation}
% begin{macrocode}
%<*class>
% end{macrocode}
% begin{macrocode}
LoadClass{minimal}
% end{macrocode}
% begin{macrocode}
RequirePackage[utf8]{inputenc}
RequirePackage[T1]{fontenc}
RequirePackage[english]{babel}
RequirePackage{newunicodechar}
newunicodechar{⸗}{hyphen}
% end{macrocode}
% begin{macrocode}
%</class>
% end{macrocode}
% Finale
endinput
edited 14 hours ago
answered 15 hours ago
David CarlisleDavid Carlisle
498k4111441893
498k4111441893
add a comment |
add a comment |
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.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f426819%2fproblem-with-dtx-file-after-latex-kernel-upgrade-2018-04-01%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
2
There was a commit on the LaTeX2e git (github.com/latex3/latex2e/commit/…) that changed something for docstrip following github.com/latex3/latex2e/issues/34. I don't think that version has been released, the changes certainly have not made it to my MikTeX yet (updated this morning).
– moewe
Apr 16 '18 at 13:20
github.com/latex3/latex2e/issues/34 Also mentions putting
UseRawInputEncodingat the top of the.insfile to solve this. For me that generates an unknown control sequence, though when running the.dtxwith pdfTeX. And I get Unicode character not set up for use when running with pdfLaTeX.– moewe
Apr 16 '18 at 13:30
@moewe That's the answer ('the team are still covering a few cases'): do you want to post something?
– Joseph Wright♦
Apr 16 '18 at 13:57
2
@JosephWright Well, if someone who actually knows what is going on can give an answer with a workaround that works out of the box in this case, that is probably preferable to my answer just linking to the issue on GitHub.
– moewe
Apr 16 '18 at 14:08
@JosephWright Should this problem be solved in PL4? Part of it seems to be resolved, but I still get
Unicode character ⸗ (U+2E17) not set up for use with LaTeX.despite/in thenewunicodechar.– moewe
May 5 '18 at 14:15