## LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

 Options: Use Classic View Use Monospaced Font Show Text Part by Default Show All Mail Headers Topic: [<< First] [< Prev] [Next >] [Last >>]

 Re: latex/3480: Support for UTF-8 missing in inputenc.sty Dominique Unruh <[log in to unmask]> Sun, 19 Jan 2003 22:30:33 +0100 text/plain (47 lines) > sorry, misunderstanding, i meant quite literally the semantics of the > arguments for your \DeclareUnicodecharacter macro, ie what goes into > #1 ... Ah. \DeclareUnicodeCharacter{}{} where is a TeX number (it is normalised by using \number#1), and is some TeX code (like \texthallo). > question is how both could coexist and if they can whether they can use the > same database of \DeclareUnicodecharacter declarations rather than doubling > the space My package uses features like combining characters and options, and therefore has to reflect these in the database (the database does not use \DeclareUnicodeCharacter, which is only an abbreviation). Further the files are ordered by code position uni-.def, and not by fontencoding, since they are loaded on demand. But now that I think of it, it would make sense to allow third party packages to add mappings without having to detect, which package is loaded. This would be possible by adapting the syntax of your \DeclareUnicodeCharacter to mine (should'nt be too hard, exactly one byte has to be changed in \DeclareUnicodeCharacter), and then not simply \def'ing it, but using % pseudo-code \ifx\DeclareUnicodeCharacter\undefined\let\DeclareUnicodeCharacter\empty\fi \g@addtomacro\DeclareUnicodeCharacter{the code} in both utf8.def's. This would make \DeclareUnicodeCharacter declare for both packages. > > > > \DeclareUnicodeCommand (analogous to \DeclareTextCommand) > > \DeclareUnicodeMapping % the LaTeX may be guessed > > \DeclareUnicodeInput % like in inputenc > > \DeclareUnicodeInputText % like in inputenc If we take up the above proposal, then we don't have to worry about that any more. DniQ.