| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
name so that example hang's off of RegisterAlias method in documentation
|
|
|
|
functionality
|
|
|
|
|
|
|
|
https://github.com/danmeyers/gofpdf into danmeyers-get-barcode-dims_prevent-scaling
|
|
dimensions
|
|
|
|
|
|
|
|
Adjust the wording so GitHub parses file properly
|
|
So it is automatically parsed by GitHub
|
|
|
|
This comparison step started as a means of assuring repeatability across platforms, but has been an ongoing source of frustration with ordering of internal dictionaries and resources.
|
|
Add "Tabloid" page size, 11 x 17 inches according to ANSI X3.151.
|
|
|
|
|
|
with reference files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
document is in error state
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Fixed heading in README.md
* Fixed example heading
|
|
* Accept interfaces where appropriate.
`Fpdf.RawWriteBuf` only needs an `io.Reader`, it doesn't have to be a `bytes.Buffer`.
The only reason I can see not to do this is to avoid the interface "boxing" if the caller is actually using a `bytes.Buffer`;
however, since eventually this gets into `binary.Read` which takes an `io.Reader` the boxing will happen anyway (and possibly repeatedly if `readByte` gets called a number of times; I didn't bother to check).
* Also use interface for segmentRead
* Use read-only bytes.Reader instead of bytes.Buffer where appropriate.
|
|
|
|
* Add RegisterAztec
* Add test for RegisterAztec
|
|
|
|
Flores
|
|
|
|
|
