witwall / origami-pdf

Automatically exported from code.google.com/p/origami-pdf
GNU Lesser General Public License v3.0
0 stars 0 forks source link

Error on saving obfuscated pdf #12

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.run bug.rb (see attachment - it's modified 
"samples\actions\launch\winparams.rb")

What is the expected output? What do you see instead?
Origami can't save obfuscated PDF:

/origami/obfuscation.rb:192:in `to_s': wrong number of arguments(1 for 0) 
(ArgumentError)
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/lib/origami/obfuscation.rb:192:in `block in to_obfuscated_str'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/lib/origami/obfuscation.rb:190:in `gsub!'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/lib/origami/obfuscation.rb:190:in `to_obfuscated_str'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/lib/origami/obfuscation.rb:121:in `block in to_obfuscated_str'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/lib/origami/obfuscation.rb:119:in `each_pair'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/lib/origami/obfuscation.rb:119:in `to_obfuscated_str'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/lib/origami/obfuscation.rb:223:in `to_obfuscated_str'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/lib/origami/pdf.rb:1020:in `block in output'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/lib/origami/pdf.rb:892:in `each'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/lib/origami/pdf.rb:892:in `output'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/lib/origami/pdf.rb:299:in `save'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/origami-1.2.3/samples/actions/launch/test.rb:22:in `<main>'

What version of the product are you using? On what operating system?
- Origami gem v.1.2.3
- Ruby 1.9.3 on Windows XP

Please provide any additional information below.

Original issue reported on code.google.com by reapedbr...@bk.ru on 21 Feb 2012 at 11:53

Attachments: