akira/pdfjs-dist - pdfjs-dist - Gitea: Git with a cup of tea

Tree: 9742e58275

Author	SHA1	Message	Date
Jonas Jenwald	40feca12c1	Ignore line-breaks between operator and digit in `Lexer.getNumber` This is consistent with the behaviour in Adobe Reader (and PDFium), and it fixes the display of page 30 in https://bug1354114.bmoattachments.org/attachment.cgi?id=8855457 (taken from https://bugzilla.mozilla.org/show_bug.cgi?id=1354114). The patch also makes the `error` message for invalid numbers slightly more useful, by including the charCode as well. (Having that information available would have reduced the time spent on debugging the PDF file above.)	8 years ago
Tim van der Meij	35730148a7	Convert the files in the `/test/unit` folder to ES6 modules	8 years ago
porlan1	d9e1cb7955	unit test files as UMD modules	8 years ago
Jonas Jenwald	c850968fa7	Remove `globals` that are now unnecessary thanks to the use of various ESLint environments (e.g. Node, ShellJS, Jasmine)	8 years ago
Jonas Jenwald	995e1a45b8	Ensure that `Lexer_getName` does not fail if a `Name` contains in invalid usage of the NUMBER SIGN (#) (issue 6692) This is a regression from PR 3424. The PDF file in the referenced issue is using `Type3` fonts. In one of those, the `/CharProcs` dictionary contains an entry with the name `/#`. Before the changes to `Lexer_getName` in PR 3424, we were allowing certain invalid `Name` patterns containing the NUMBER SIGN (#). It's unfortunate that this has been broken for close to two and a half years before the bug surfaced, but it should at least indicate that this is not a widespread issue. Fixes 6692.	10 years ago
Manas	a2ba1b8189	Uses editorconfig to maintain consistent coding styles Removes the following as they unnecessary /* -- Mode: Java; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -- / / vim: set shiftwidth=2 tabstop=2 autoindent cindent expandtab: */	10 years ago
Jonas Jenwald	0edb520a10	Add unit-tests for Linearization dictionary parsing (PR 5023 follow-up) This should really have been part of 5023, but better late than never I suppose.	10 years ago
Jonas Jenwald	c718d1ab10	Ignore double negative in `Lexer_getNumber` (issue 6218) Basic mathematics would suggest that a double negative should always become positive, but it appears that Adobe Reader simply ignores that case. Hence I think that it makes sense for us to do the same. Fixes 6218.	10 years ago
Collin Anderson	54e984c763	cleaned whitespace	10 years ago
Yury Delendik	20a91bcdbf	Fixes ignoring of the escaped CR LF	11 years ago
Jonas Jenwald	7d4acc13fb	Fix coding style in test/unit/parser_spec.js	11 years ago
Ophir LOJKINE	4a66eccedc	Rewrite Lexer_getNumber. Now, it computes the numbers with only basic arithmetic operations, without first creating a string and then calling parseFloat. The new function doesn't behave exactly the same as the old one. In particular, the old behaviour was that when there was a number immediatly followed by an 'E', the 'E' was consumed. Now it's not. It allows for "glued" numbers and operators. Also, the new function is faster and consumes less memory.	11 years ago
Yury Delendik	19e8f2f059	lookChar refactoring	12 years ago
Yury Delendik	95e5429707	Fixes getString	12 years ago
Yury Delendik	81f8f92696	Adds web/* and test/* for jshint target	12 years ago
mduan	eb8f4e8343	Handle some illegal characters in hex string Do not throw exception when hex strings are in the wrong format Currently pdf.js is throwing an exception for the following hex string: `<7 0 2 15 5 2 2 2 4 3 2 4>` The issue is that the 15 is not a valid hex character so pdf.js ends up throwing an exception. This diff changes the parser to process the above hex string as follow: `70 21 55 2 24 32` (Note: the final 4 of the hex string is ignored) replicating the behaviour of MuPDF, and doesn't throw an exception.	12 years ago
Yury Delendik	4c0f9eb924	Fixes getNumber at the end of stream	13 years ago