- ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-377 ] unqoute image filenames not only on windows
by noreply＠sarovar.org 05 Jul '05

05 Jul '05

Bugs item #377, was opened at 2005-07-02 21:43 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106 Category: Image inclusion Group: None Status: Open Resolution: None Priority: 5 Submitted By: Georg Baum (baum) Assigned to: Martin Schröder (oneiros) Summary: unqoute image filenames not only on windows Initial Comment: The file pdftex-1.30.0-rc1/src/texk/web2c/pdftexdir/writeimg.c contains in the function readfile() a code block to unqoute file names which is inside #ifdef WIN32 ... #endif. This code should be enabled on all platforms (or at least on linux), since quoted filenames (which are necessary if the name contains spaces) do not only work well on linux. Thanks, Georg ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2005-07-05 10:57 Message: Logged In: YES user_id=1276 Hello, > I manually copied and cited your message because I could > not find out how to do that correctly with the tracker > system :-( Also the tiny typein area and the order of postings is very annoying. Perhaps we should better continue the discussion on the ntg-pdftex mailing list. >> Now you want the limitation of windows that quotes >> cannot be used apply on the other systems? > > I want to trade in the use of quotes for the use of > spaces. > Since you can only have one (not really, see below) it is > from a user's point of view better to support spaces on > all > platforms and not spaces on windows and quotes on other > platforms. >From a user's point it is better to support all characters instead of randomly choosen ones. The quoting method makes things worse: * There is no method to detect, whether quoting is supported: \includegraphics{"abc def.png"} The graphics package does not know, whether the TeX compiler will look for {abc def.png}, {"abc def.png"}, or {"abc}. Now you cannot use *both* quotes *and* spaces. * A very long time, spaces are considered "fancy" in file names, it is asking for trouble, because they are not supported on DOS file systems. But nowadays, spaces become "normal" despite the trouble (also on windows systems). The difference in our problem descriptions seems to be that you want to have *spaces* as usable characters in filenames, my conclusion is that we must allow *any* character as usable. Otherwise we will have bug reports about quotes. * And if we have a solution with *all* characters, there will be no problems with different encodings including ucs-2 or ucs-4. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- Comment By: Georg Baum (baum) Date: 2005-07-04 18:55 Message: Logged In: YES user_id=2590 Hello, I manually copied and cited your message because I could not find out how to do that correctly with the tracker system :-( > I must disagree, "the same behaviour on all platforms" > can not mean to add the limitations of all platforms. No, that is not my intention. > Now you want the limitation of windows that quotes > cannot be used apply on the other systems? I want to trade in the use of quotes for the use of spaces. Since you can only have one (not really, see below) it is from a user's point of view better to support spaces on all platforms and not spaces on windows and quotes on other platforms. > There are operating systems that deal with 8+3 file > names only. Do you want to forbid long file names, > for example? Of course not. > Thus we are loosing both quotes and spaces. Spaces still > cannot be used in general. Other TeX engines > does not know about quoting. There is no secure way > to know, whether quoting is working. Thus code that > is intended for different systems must avoid spaces. And quotes (in the filename itself, not for quoting), so this is not really an argument to support them. Concerning other implementations: \includegraphics{foo.png} does not work with plain latex, but with pdflatex. The same would apply to spaces in filenames, so I see no big problem there. > And the current quoting scheme does not solve the > problem at all, it moves the problem from spaces to > quotes, spaces can still not be used and quotes are > now made unavailable. Also the quoting scheme does > not allow quoting of the quotes themselves. It does (although I am not sure whether that is intended): Only the first quote is stripped from two consecutive quotes, e.g. the string '"a""bc"' is transformed into 'a"bc'. > A solution would allow *all* characters. > The solution should be able to deal with utf-8 or > even ucs-2/4 encoded file names. Agreed. If you think that the quoting is so bad then why not remove it altogether and tell users to use \pdfximage? My problem with the current implementation is the inconsistency: If filenames with spaces work on windows if quoted, I expect that they work on linux, too, since the OS supports them. Of course I can't expect the same from filenames with quotes: They are not supported by windows, so they can't be supported by pdftex on windows. I hope I have made my point clear. I can live with it if you still don't agree, so I'll stop arguing now. Georg ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2005-07-04 16:07 Message: Logged In: YES user_id=1276 Hello, I must disagree, "the same behaviour on all platforms" can not mean to add the limitations of all platforms. Now you want the limitation of windows that quotes cannot be used apply on the other systems? There are operating systems that deal with 8+3 file names only. Do you want to forbid long file names, for example? Thus we are loosing both quotes and spaces. Spaces still cannot be used in general. Other TeX engines does not know about quoting. There is no secure way to know, whether quoting is working. Thus code that is intended for different systems must avoid spaces. And the current quoting scheme does not solve the problem at all, it moves the problem from spaces to quotes, spaces can still not be used and quotes are now made unavailable. Also the quoting scheme does not allow quoting of the quotes themselves. A solution would allow *all* characters. The solution should be able to deal with utf-8 or even ucs-2/4 encoded file names. That is already given by the syntax of \pdfximage. Thus new primitives \pdfinput, \pdfopenin, \pdfopenout with <general text> would allow any file name and a macro code can test, whether this feature is available by testing the command names. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- Comment By: Georg Baum (baum) Date: 2005-07-04 13:46 Message: Logged In: YES user_id=2590 I agree that the quote stripping is a hack and should eventually be replaced by something better. I do think however that the behaviour on all platforms should be the same if it is at all possible. Right now, filenames with quotes work on linux and not on windows, and quoted filenames with spaces work on windows but not on linux. Thanks for the hint to pdfximage, I did not know about that (coming from standard LaTeX and always using \includegraphics} Georg ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2005-07-04 13:13 Message: Logged In: YES user_id=1276 Hello, it is a very bad idea, quotes are perfectly legal in linux and other operating systems. Also image inclusion is done by \pdfximage that uses <general text>, by <general text>, text surrounded by curly braces (catcode 1 and 2) *all* possible file names can be given including quotes and spaces. We need rather new primitives for \input, \openin, and \openout to provide the file names as <general text>. The all file names can be given without the need of quoting at all. See also the discussion about \pdfinput in the ntg-pdftex mailing list. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106

1 0

[ pdftex-Bugs-377 ] unqoute image filenames not only on windows
by noreply＠sarovar.org 04 Jul '05

04 Jul '05

Bugs item #377, was opened at 2005-07-02 21:43 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106 Category: Image inclusion Group: None Status: Open Resolution: None Priority: 5 Submitted By: Georg Baum (baum) Assigned to: Martin Schröder (oneiros) Summary: unqoute image filenames not only on windows Initial Comment: The file pdftex-1.30.0-rc1/src/texk/web2c/pdftexdir/writeimg.c contains in the function readfile() a code block to unqoute file names which is inside #ifdef WIN32 ... #endif. This code should be enabled on all platforms (or at least on linux), since quoted filenames (which are necessary if the name contains spaces) do not only work well on linux. Thanks, Georg ---------------------------------------------------------------------- >Comment By: Georg Baum (baum) Date: 2005-07-04 18:55 Message: Logged In: YES user_id=2590 Hello, I manually copied and cited your message because I could not find out how to do that correctly with the tracker system :-( > I must disagree, "the same behaviour on all platforms" > can not mean to add the limitations of all platforms. No, that is not my intention. > Now you want the limitation of windows that quotes > cannot be used apply on the other systems? I want to trade in the use of quotes for the use of spaces. Since you can only have one (not really, see below) it is from a user's point of view better to support spaces on all platforms and not spaces on windows and quotes on other platforms. > There are operating systems that deal with 8+3 file > names only. Do you want to forbid long file names, > for example? Of course not. > Thus we are loosing both quotes and spaces. Spaces still > cannot be used in general. Other TeX engines > does not know about quoting. There is no secure way > to know, whether quoting is working. Thus code that > is intended for different systems must avoid spaces. And quotes (in the filename itself, not for quoting), so this is not really an argument to support them. Concerning other implementations: \includegraphics{foo.png} does not work with plain latex, but with pdflatex. The same would apply to spaces in filenames, so I see no big problem there. > And the current quoting scheme does not solve the > problem at all, it moves the problem from spaces to > quotes, spaces can still not be used and quotes are > now made unavailable. Also the quoting scheme does > not allow quoting of the quotes themselves. It does (although I am not sure whether that is intended): Only the first quote is stripped from two consecutive quotes, e.g. the string '"a""bc"' is transformed into 'a"bc'. > A solution would allow *all* characters. > The solution should be able to deal with utf-8 or > even ucs-2/4 encoded file names. Agreed. If you think that the quoting is so bad then why not remove it altogether and tell users to use \pdfximage? My problem with the current implementation is the inconsistency: If filenames with spaces work on windows if quoted, I expect that they work on linux, too, since the OS supports them. Of course I can't expect the same from filenames with quotes: They are not supported by windows, so they can't be supported by pdftex on windows. I hope I have made my point clear. I can live with it if you still don't agree, so I'll stop arguing now. Georg ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2005-07-04 16:07 Message: Logged In: YES user_id=1276 Hello, I must disagree, "the same behaviour on all platforms" can not mean to add the limitations of all platforms. Now you want the limitation of windows that quotes cannot be used apply on the other systems? There are operating systems that deal with 8+3 file names only. Do you want to forbid long file names, for example? Thus we are loosing both quotes and spaces. Spaces still cannot be used in general. Other TeX engines does not know about quoting. There is no secure way to know, whether quoting is working. Thus code that is intended for different systems must avoid spaces. And the current quoting scheme does not solve the problem at all, it moves the problem from spaces to quotes, spaces can still not be used and quotes are now made unavailable. Also the quoting scheme does not allow quoting of the quotes themselves. A solution would allow *all* characters. The solution should be able to deal with utf-8 or even ucs-2/4 encoded file names. That is already given by the syntax of \pdfximage. Thus new primitives \pdfinput, \pdfopenin, \pdfopenout with <general text> would allow any file name and a macro code can test, whether this feature is available by testing the command names. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- Comment By: Georg Baum (baum) Date: 2005-07-04 13:46 Message: Logged In: YES user_id=2590 I agree that the quote stripping is a hack and should eventually be replaced by something better. I do think however that the behaviour on all platforms should be the same if it is at all possible. Right now, filenames with quotes work on linux and not on windows, and quoted filenames with spaces work on windows but not on linux. Thanks for the hint to pdfximage, I did not know about that (coming from standard LaTeX and always using \includegraphics} Georg ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2005-07-04 13:13 Message: Logged In: YES user_id=1276 Hello, it is a very bad idea, quotes are perfectly legal in linux and other operating systems. Also image inclusion is done by \pdfximage that uses <general text>, by <general text>, text surrounded by curly braces (catcode 1 and 2) *all* possible file names can be given including quotes and spaces. We need rather new primitives for \input, \openin, and \openout to provide the file names as <general text>. The all file names can be given without the need of quoting at all. See also the discussion about \pdfinput in the ntg-pdftex mailing list. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106

1 0

Patch EscapeAndOther
by Heiko Oberdiek 04 Jul '05

04 Jul '05

Hello, I have uploaded the patch EscapeAndOther, #375. The patch is based on pdftex-1.30.0-rc1. It supersedes patch EscapeDivers.tar.bz2, #371. Inherited from patch EscapeDivers: Expandable: \pdfstrcmp, \pdfescapestring, \pdfescapename Added: \pdfescapehex, \pdfunescapehex Fix: \pdfescapename: '%' is also a delimiter that needs escaping. New in patch EscapeAndOther: * \pdfcreationdate * \pdffilemoddate * \pdffilesize * \pdfmdfivesum * \pdffiledump * \pdfshellescape * \pdfmatch and \pdflastmatch * Start with bug fix: quotes are legal in other operating systems than windows. Syntax: %% expandable commands: \pdfstrcmp <general text> <general text> \pdfescapestring <general text> \pdfescapename <general text> \pdfescapehex <general text> \pdfunescapehex <general text> \pdfcreationdate \pdffilemoddate <general text> \pdffilesize <general text> \pdfmdfivesum <file spec> | <general text> \pdfmatch <match options> <general text> <general text> <match options> := [icase] [subcount <number>] \pdflastmatch <number> %% read-only integers \pdfshellescape Common for the following primitives: * The result string is given by characters with catcode "other" (12), only the space has catcode "space" (10). The commands follow the tradition of \meaning, \string, ... * The argument <general text> is expanded before use. It follows the tradition of \special, \message, \pdfobj, ... Description: \pdfstrcmp{<a>}{} Compares two strings and returns the strings "0" if <a> equals "-1" if <a> is less than "1" if <a> is greater than Use example: \ifcase\pdfstrcmp{abc}{def}\relax \message{abc = def} \or \message{abc > def} \else \message{abc < def} \fi Alternative: Implementing as read-only integer, then the use in \ifcase, \ifnum, ... is more save: \ifcase\pdfstrcmp{xyz}{abc}1\or 2\else 3\fi expands to 3, as read-only integer it expands to the expected 2. \pdfescapestring{<a>} Escapes the string <a> that it can be used as PDF string. '(', ')', '\' are escaped along with the control and 8-bit characters. Use example: \pdfinfo{/Title (\pdfescapestring{...})} \special{ps: [ /Title (\pdfescapestring{...}) /DOCINFO pdfmark} Alternative: Perhaps 8-bit characters don't need escaping. Whitespace, especially newlines should be escaped, because of the use for latex/dvips to avoid recoding problems (<LF> -> <CR><LF>). \pdfescapename{<a>} Escapes the string <a> that it can be used as PDF string. Whitespace, delimiters, '#' are escaped along with the control and 8-bit characters, recommended by the spec. Use example: \pdfobj stream attr{/Type/EmbeddedFile% /Subtype/\pdfescapename{text/plain; charset=iso-8859-1}% ... } file {...} \pdfescapehex{<a>}, \pdfunescapehex{} String <a> is converted to uppercase hexadecimal representation, is converted back. Use example: \pdfescapehex{Hello} is converted to 48656C6C6F \pdfinfo{/Title <\pdfescapehex{Hello}>} Also it can be used to write strings in auxiliary files and later reread without worrying about catcodes, unmached curly braces. \pdfcreationdate It expands to the date string that pdfTeX uses in the info dict as default. Rationale: * It provides seconds and especially the time zone. * Setting of /M date for annotations. * Because of the complicate change file structure of the sources it is not easy to synchronize the creation date with \year, \month, \day and \time. Thus \pdfcreationdate can be used to set these registers to the same values. Example: \pdfcreationdate expands to D:20050625015605+02'00' \pdfannot ...{/Subtype /FileAttachment \M (\pdfcreationdate) ...} \pdffilemoddate{<file>} It expands to the modification date of <file> in the same format as \pdfcreationdate (PDF date format). On error it returns the empty string. Rationale: * File embedding: the date is shown in the attachment tab. * "Make feature": files can be compared, it can be checked, which file is newer. Example: pdfTeX does not support EPS files, epstopdf.sty converts them to PDF either always or, if the PDF variants do not exists. Both ways are not satifactory, either the time penalty is large or pdf files are embedded that are out of date. \pdffilemoddate solves this problem. Error handling, see \pdffilesize I don't have implemented a \pdfcreationdate because of portability issue: The "ctime" field of struct "stat" is interpreted differently among operating systems: * creation date, e.g. win * inode change time, e.g. unix \pdffilesize{<file>} It expands to the size of <file> as string. On error it returns the empty string. Rationale: * File embedding: the size is shown in the attachment tab. * Sometimes it is useful to know if a file has size "0" (failed conversions, ...). Error handling: Currently the empty string is silently returned. Alternatives: * Stop with error message. But what can the user do? Error recovery is easy: no information available, thus return nothing. * Warning message. But the primitives could be used for checks on file existence. * Return status in \pdfretval. I doubt a little whether this is really necessary. It is very easy to implement. But the documentation grows by a large list of error codes with its problems: Much to explain to the users. How they are assigned? \pdfmdfivesum{<abc>} or \pdfmdfivesum file {<file>} It calculates the md5 sum and converts it to uppercase hexadecimal format (same as \pdfescapehex). The syntax is a simplified \pdfobj: Either the data is given directly or in a file. Rationale: * File embedding: providing /CheckSum. * Also the md5 sums of auxiliary files could be stored and compared in order to display a rerun warning. (Of course, it can be possible that different files have the same checksum, but the same file does not have different checksums.) \pdfshellescape It is a read-only integer that is 1 if \write18 is enabled, 0 otherwise. Rationale: * It thought that \ifeof18 with \pdftexversion to implement a safe test for the \write18 feature. But I had to learn that I was wrong, see thread in comp.text.tex: "Confused about pstricks and pdftricks": mikTeX's pdfTeX does not implement \ifeof18. For implementing the test, only a obscure way via \pdftexbanner remains, but this way is not very reliable, the contents of \pdftexbanner is not well defined, it could be anything. Quotes in file names: * File name handling is quite chaotic. Quotes are removed by the scanner for \input, \open*. This behaviour is schizophrene: to solve a problem with spaces, quotes are now forbidden. * Inconsistencies: The syntax of \pdfobj and \pdfximage would allow any file name, but \pdfobj removes quotes, only \pdfximage uses the more intelligent way, it removes quotes for windows only. Thus the patch fixes: * append_to_name (used in pack_file_name): quotes are removed for windows only. This fixes \pdfobj. * utils.c: new function "makecfilename", used by \pdfximage (readimage), \pdffilesize, ... \pdfmatch [icase] [subcount <number>}] {<pattern>}{<string>} Implements pattern matching using the POSIX regex (a standard library at least in my linux). It returns the same values as \pdfstrcmp, but with the following semantics: -1: error case (invalid pattern, ...) 0: no match 1: match found Options: * icase: case insensitive matching * subcount: it sets the table size for found subpatterns. A number "-1" resets the table size to the start default. See the manual page regex.3 and regex.7. The implementation shows a possible interface to pattern matching in TeX. Therefore only the basics is implemented. Flags: * REG_EXTENDED is set in the implementation. * REG_ICASE: can be set by user. * other: not implemented. \pdflastmatch <number> The result of \pdfmatch is stored in an array. The entry "0" contains the match, the following entries submatches. The positions of the matches are also available. They are encoded in the following manner to avoid another primitive: <position> "->" <match string> "->" is used as separator in the tradition of \meaning. There exists macros for parsing the output of \meaning (e.g. in LaTeX: \strip@prefix). The position "-1" with an empty string indicates that this entry is not set. Example: \def\msg#{\immediate\write16 } \msg{\pdfmatch{(l+)o (W(o))}{Hello World}} \msg{\pdflastmatch0} \msg{\pdflastmatch1} \msg{\pdflastmatch2} \msg{\pdflastmatch3} \msg{\pdflastmatch4} Result: 1 2->llo Wo 2->ll 6->Wo 7->o -1-> Alternative: PCRE (Perl-compatible regular expressions) is far more powerful. More options, named subpattern, ... License for 0.4 was GPL compatible, since 0.5 it is BSD, current version is 0.6. The TeX interface could be changed in the following way: * Addition: \pdflastmatchbyname <general text> It extracts matches for named subpattern. * Options can be given by the same name as in the PCRE description: \pdfmatch anchored caseless ... {}{} For easier/faster scanning the options could be restricted to be given in sorted order. * Or options can be given by letters in any order in an additional argument: \pdfmatch{<pattern>}{<options>}{<string>} \pdfmatch{l+}{ai}{Hello World} The implementation could then use strchr to check, whether an option is set. Patch instructions for testing are given in the patch description at sarovar. Have fun Heiko <oberdiek(a)uni-freiburg.de> --

4 13

[ pdftex-Bugs-377 ] unqoute image filenames not only on windows
by noreply＠sarovar.org 04 Jul '05

04 Jul '05

Bugs item #377, was opened at 2005-07-02 21:43 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106 Category: Image inclusion Group: None Status: Open Resolution: None Priority: 5 Submitted By: Georg Baum (baum) Assigned to: Martin Schröder (oneiros) Summary: unqoute image filenames not only on windows Initial Comment: The file pdftex-1.30.0-rc1/src/texk/web2c/pdftexdir/writeimg.c contains in the function readfile() a code block to unqoute file names which is inside #ifdef WIN32 ... #endif. This code should be enabled on all platforms (or at least on linux), since quoted filenames (which are necessary if the name contains spaces) do not only work well on linux. Thanks, Georg ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2005-07-04 16:07 Message: Logged In: YES user_id=1276 Hello, I must disagree, "the same behaviour on all platforms" can not mean to add the limitations of all platforms. Now you want the limitation of windows that quotes cannot be used apply on the other systems? There are operating systems that deal with 8+3 file names only. Do you want to forbid long file names, for example? Thus we are loosing both quotes and spaces. Spaces still cannot be used in general. Other TeX engines does not know about quoting. There is no secure way to know, whether quoting is working. Thus code that is intended for different systems must avoid spaces. And the current quoting scheme does not solve the problem at all, it moves the problem from spaces to quotes, spaces can still not be used and quotes are now made unavailable. Also the quoting scheme does not allow quoting of the quotes themselves. A solution would allow *all* characters. The solution should be able to deal with utf-8 or even ucs-2/4 encoded file names. That is already given by the syntax of \pdfximage. Thus new primitives \pdfinput, \pdfopenin, \pdfopenout with <general text> would allow any file name and a macro code can test, whether this feature is available by testing the command names. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- Comment By: Georg Baum (baum) Date: 2005-07-04 13:46 Message: Logged In: YES user_id=2590 I agree that the quote stripping is a hack and should eventually be replaced by something better. I do think however that the behaviour on all platforms should be the same if it is at all possible. Right now, filenames with quotes work on linux and not on windows, and quoted filenames with spaces work on windows but not on linux. Thanks for the hint to pdfximage, I did not know about that (coming from standard LaTeX and always using \includegraphics} Georg ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2005-07-04 13:13 Message: Logged In: YES user_id=1276 Hello, it is a very bad idea, quotes are perfectly legal in linux and other operating systems. Also image inclusion is done by \pdfximage that uses <general text>, by <general text>, text surrounded by curly braces (catcode 1 and 2) *all* possible file names can be given including quotes and spaces. We need rather new primitives for \input, \openin, and \openout to provide the file names as <general text>. The all file names can be given without the need of quoting at all. See also the discussion about \pdfinput in the ntg-pdftex mailing list. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106

1 0

[ pdftex-Bugs-377 ] unqoute image filenames not only on windows
by noreply＠sarovar.org 04 Jul '05

04 Jul '05

Bugs item #377, was opened at 2005-07-02 21:43 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106 Category: Image inclusion Group: None Status: Open Resolution: None Priority: 5 Submitted By: Georg Baum (baum) Assigned to: Martin Schröder (oneiros) Summary: unqoute image filenames not only on windows Initial Comment: The file pdftex-1.30.0-rc1/src/texk/web2c/pdftexdir/writeimg.c contains in the function readfile() a code block to unqoute file names which is inside #ifdef WIN32 ... #endif. This code should be enabled on all platforms (or at least on linux), since quoted filenames (which are necessary if the name contains spaces) do not only work well on linux. Thanks, Georg ---------------------------------------------------------------------- >Comment By: Georg Baum (baum) Date: 2005-07-04 13:46 Message: Logged In: YES user_id=2590 I agree that the quote stripping is a hack and should eventually be replaced by something better. I do think however that the behaviour on all platforms should be the same if it is at all possible. Right now, filenames with quotes work on linux and not on windows, and quoted filenames with spaces work on windows but not on linux. Thanks for the hint to pdfximage, I did not know about that (coming from standard LaTeX and always using \includegraphics} Georg ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2005-07-04 13:13 Message: Logged In: YES user_id=1276 Hello, it is a very bad idea, quotes are perfectly legal in linux and other operating systems. Also image inclusion is done by \pdfximage that uses <general text>, by <general text>, text surrounded by curly braces (catcode 1 and 2) *all* possible file names can be given including quotes and spaces. We need rather new primitives for \input, \openin, and \openout to provide the file names as <general text>. The all file names can be given without the need of quoting at all. See also the discussion about \pdfinput in the ntg-pdftex mailing list. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106

1 0

input
by Hans Hagen 04 Jul '05

04 Jul '05

Hi, how about \pdfinput {filename} \pdfopenin {filename} \pdfopenout {filename} and maybe even one that accepts a hex encoded string \pdfinput hex {filename} \pdfopenin hex {filename} \pdfopenout hex {filename} Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

4 11

\pdfpagesresources?
by Pawel Jackowski 04 Jul '05

04 Jul '05

Hi there, what do you think about adding \pdfpagesresources primitive toks list? > Thanh: > the answer is simple: nobody ever asked for it, and I don't > need it for myself :). If considered it can be added without > problems. I agree we can live without \pdfpagesresources, as well as we could without \pdfpagesattr. Hovever, collecting named resources per document is much easier than per page. In many cases we don't need different /Resources dict for each page and globally assigned (identical) \pdfpageresources toks list is unnecessarily written into PDF output each time the page is shipped out. It makes a difference for big documents. Of course one can save some time and space by writing resources as objects and storing object rerefences in \pdfpageresources. But to make things cool I'd opt to add primitive \pdfpagesresources toks list. ? -- Pawe/l Jackowski P.Jackowski(a)gust.org.pl

3 6

[ pdftex-Bugs-377 ] unqoute image filenames not only on windows
by noreply＠sarovar.org 04 Jul '05

04 Jul '05

Bugs item #377, was opened at 2005-07-02 21:43 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106 Category: Image inclusion Group: None Status: Open Resolution: None Priority: 5 Submitted By: Georg Baum (baum) Assigned to: Martin Schröder (oneiros) Summary: unqoute image filenames not only on windows Initial Comment: The file pdftex-1.30.0-rc1/src/texk/web2c/pdftexdir/writeimg.c contains in the function readfile() a code block to unqoute file names which is inside #ifdef WIN32 ... #endif. This code should be enabled on all platforms (or at least on linux), since quoted filenames (which are necessary if the name contains spaces) do not only work well on linux. Thanks, Georg ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2005-07-04 13:13 Message: Logged In: YES user_id=1276 Hello, it is a very bad idea, quotes are perfectly legal in linux and other operating systems. Also image inclusion is done by \pdfximage that uses <general text>, by <general text>, text surrounded by curly braces (catcode 1 and 2) *all* possible file names can be given including quotes and spaces. We need rather new primitives for \input, \openin, and \openout to provide the file names as <general text>. The all file names can be given without the need of quoting at all. See also the discussion about \pdfinput in the ntg-pdftex mailing list. Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106

1 0

[ pdftex-Patches-376 ] Uniform and Normal Distribution Pseudo-random numbers patch
by noreply＠sarovar.org 03 Jul '05

03 Jul '05

Patches item #376, was opened at 2005-06-27 16:45 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=376&group_id=106 Category: Primitives Group: v1.30.0 Status: Open Resolution: None Priority: 5 Submitted By: Taco Hoekwater (taco) Assigned to: Nobody (None) Summary: Uniform and Normal Distribution Pseudo-random numbers patch Initial Comment: See the patch file itself or the mailing list for actual usage and comments. Requested by Pawel. It is intented to be applied after tex.pch (as usual) ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=376&group_id=106

4 4

[ pdftex-Bugs-377 ] unqoute image filenames not only on windows
by noreply＠sarovar.org 02 Jul '05

02 Jul '05

Bugs item #377, was opened at 2005-07-02 21:43 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106 Category: Image inclusion Group: None Status: Open Resolution: None Priority: 5 Submitted By: Georg Baum (baum) Assigned to: Martin Schröder (oneiros) Summary: unqoute image filenames not only on windows Initial Comment: The file pdftex-1.30.0-rc1/src/texk/web2c/pdftexdir/writeimg.c contains in the function readfile() a code block to unqoute file names which is inside #ifdef WIN32 ... #endif. This code should be enabled on all platforms (or at least on linux), since quoted filenames (which are necessary if the name contains spaces) do not only work well on linux. Thanks, Georg ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=377&group_id=106

2 1