Re: [poppler] Contributing to Poppler

2017-04-21 Thread Albert Astals Cid 
El divendres, 21 d’abril de 2017, a les 13:32:05 CEST, Simon Shugar va 
escriure:
> Hi Albert,
> 
> Thanks for getting back to me. What I am not sure about is how to create
> and send a patch.

git diff

will give you a nicely formatted patch.

Cheers,
  Albert

> 
> Ideally I'd like to tackle a few of the defects on Bugzilla. Like this one;
> https://bugs.freedesktop.org/show_bug.cgi?id=88242
> 
> Kind regards,
> Simon Lee Shugar
> 
> --
> 
> [image: Veeva Systems - Zinc Team]
> 
> *Simon Shugar*
> Software Engineer
> *Veeva Systems *
> simon.shu...@veeva.com
> www.veeva.com
> 
> *This email and the information it contains are intended for the intended
> recipient only, are confidential and may be privileged information exempt
> from disclosure by law.*
> *If you have received this email in error, please notify us immediately by
> reply email and delete this message from your computer.*
> *Please do not retain, copy or distribute this email.*
> 
> On Fri, Apr 21, 2017 at 5:55 AM, Albert Astals Cid  wrote:
> > El dijous, 20 d’abril de 2017, a les 14:13:14 CEST, Simon Shugar va
> > 
> > escriure:
> > > Hello,
> > 
> > Hi
> > 
> > > I've just joined the group and would like to start contributing to
> > 
> > Poppler.
> > 
> > > I am not sure how I should go about contributing to the project, is
> > > there
> > > any documentation or instructions for the process?
> > 
> > Not really, just download the code, write any improvement/bugfix you want
> > to
> > make and send the patch.
> > 
> > We'll go on from there.
> > 
> > Do you have any specific thing you want to improve?
> > 
> > Cheers,
> > 
> >   Albert
> >   
> > > This will be the first
> > > time I have contributed to an open source project.
> > > 
> > > I am looking forward to working with you all.
> > > 
> > > Kind regards,
> > > Simon Lee Shugar
> > > 
> > > --
> > > 
> > > [image: Veeva Systems - Zinc Team]
> > > 
> > > *Simon Shugar*
> > > Software Engineer
> > > *Veeva Systems *
> > > simon.shu...@veeva.com
> > > www.veeva.com
> > > 
> > > *This email and the information it contains are intended for the
> > > intended
> > > recipient only, are confidential and may be privileged information
> > > exempt
> > > from disclosure by law.*
> > > *If you have received this email in error, please notify us immediately
> > 
> > by
> > 
> > > reply email and delete this message from your computer.*
> > > *Please do not retain, copy or distribute this email.*


___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

Re: [poppler] Contributing to Poppler

2017-04-21 Thread Simon Shugar 
Hi Albert,

Thanks for getting back to me. What I am not sure about is how to create
and send a patch.

Ideally I'd like to tackle a few of the defects on Bugzilla. Like this one;
https://bugs.freedesktop.org/show_bug.cgi?id=88242

Kind regards,
Simon Lee Shugar

--

[image: Veeva Systems - Zinc Team]

*Simon Shugar*
Software Engineer
*Veeva Systems *
simon.shu...@veeva.com
www.veeva.com

*This email and the information it contains are intended for the intended
recipient only, are confidential and may be privileged information exempt
from disclosure by law.*
*If you have received this email in error, please notify us immediately by
reply email and delete this message from your computer.*
*Please do not retain, copy or distribute this email.*

On Fri, Apr 21, 2017 at 5:55 AM, Albert Astals Cid  wrote:

> El dijous, 20 d’abril de 2017, a les 14:13:14 CEST, Simon Shugar va
> escriure:
> > Hello,
>
> Hi
>
> >
> > I've just joined the group and would like to start contributing to
> Poppler.
> > I am not sure how I should go about contributing to the project, is there
> > any documentation or instructions for the process?
>
> Not really, just download the code, write any improvement/bugfix you want
> to
> make and send the patch.
>
> We'll go on from there.
>
> Do you have any specific thing you want to improve?
>
> Cheers,
>   Albert
>
> > This will be the first
> > time I have contributed to an open source project.
> >
> > I am looking forward to working with you all.
> >
> > Kind regards,
> > Simon Lee Shugar
> >
> > --
> >
> > [image: Veeva Systems - Zinc Team]
> >
> > *Simon Shugar*
> > Software Engineer
> > *Veeva Systems *
> > simon.shu...@veeva.com
> > www.veeva.com
> >
> > *This email and the information it contains are intended for the intended
> > recipient only, are confidential and may be privileged information exempt
> > from disclosure by law.*
> > *If you have received this email in error, please notify us immediately
> by
> > reply email and delete this message from your computer.*
> > *Please do not retain, copy or distribute this email.*
>
>
>
___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

Re: [poppler] PLEASE INSUBSCRIBE ME!!!!!!!!

2017-04-21 Thread Jason Crain 
On Fri, Apr 21, 2017 at 11:24:30AM -0500, Joan Ronck wrote:
> 
> 
> Sent from my iPhone
> ___
> poppler mailing list
> poppler@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/poppler

Use the form at this link: https://lists.freedesktop.org/mailman/options/poppler
___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

[poppler] PLEASE INSUBSCRIBE ME!!!!!!!!

2017-04-21 Thread Joan Ronck 


Sent from my iPhone
___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

Re: [poppler] evince does not show chinese bold or italic

2017-04-21 Thread Jason Crain 
On Thu, Apr 20, 2017 at 05:28:08PM +0200, Thomas Johnsson wrote:
> I suspect (but I'm not sure) that acroread synthesizes bold and italic from
> the regular font, and that evince fails to do so.
> Or could it be that additional fonts need to be installed?
> Or might this have been fixed in a later version of evince?

For the benefit of the discussion, I'll repeat and expand on what I said
on the evince mailing list.

This document does not embed fonts, which means that poppler uses
fontconfig to locate appropriate substitute fonts.  If fontconfig can't
find the right combination of bold and italic, it will select some other
non-italic or non-bold variant.  My system, and apparently also William
Bader's system, at least show the bold font but not the italic font
because we have a bold CJK font installed.  I don't think that poppler
tries to synthesize font styles.

The pdf reference does mention that font styles can be synthesized, and
this might be what acroread is doing, so it would be nice if poppler
could synthesize bold or italic font styles.
___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

Re: [poppler] R: Hello

2017-04-21 Thread Jason Crain 
On Fri, Apr 21, 2017 at 03:34:12PM +0200, Amila Fernando wrote:
> Thank you very much for answering,
> 
> I still have to reveal the code even if I'm based on the poppler code but
> not completely but modifying it? And if I add new code to it, I can keep
> them hidden?

Please keep the mailing list in cc.

Any code that is considered a derivative work has to be shared under a
GPL license.  This includes modifications and additions.

There are far better summaries of the GPL on the internet than I can
provide so please read those and read the GPL license itself if you need
more specific information.

https://en.wikipedia.org/wiki/GNU_General_Public_License
https://www.gnu.org/licenses/gpl-faq.html

And the licenses:
https://cgit.freedesktop.org/poppler/poppler/tree/COPYING
or
https://cgit.freedesktop.org/poppler/poppler/tree/COPYING3
___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

[poppler] Poppler 0.54.0 released

2017-04-21 Thread Albert Astals Cid 
Available from
http://poppler.freedesktop.org/poppler-0.54.0.tar.xz

Changes against 0.53.0 include:
core:
 * Make XRef reconstruction a bit better. Bug #100509

glib:
 * Expose movie play mode. Bug #99625
 * demo: Show play mode in movie properties view

qt5:
 * Compile with -DQT_NO_CAST_FROM_BYTEARRAY. Bug #100311

utils:
 * pdfimages: don't fail listing if inline image data contains 'EI'. Bug #100737

This release was brought to you by Albert Astals Cid, Carlos Garcia Campos, 
Adrian Johnson, Christoph Cullmann, Francesco Poli

Testing, patches and bug reports welcome.

Cheers,
  Albert
___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

[poppler] 2 commits - CMakeLists.txt configure.ac cpp/Doxyfile glib/CMakeLists.txt glib/Makefile.am gtk-doc.make NEWS poppler/XRef.cc qt4/src qt5/src

2017-04-21 Thread Albert Astals Cid 
 CMakeLists.txt|2 +-
 NEWS  |   14 ++
 configure.ac  |2 +-
 cpp/Doxyfile  |2 +-
 glib/CMakeLists.txt   |2 +-
 glib/Makefile.am  |2 +-
 gtk-doc.make  |1 +
 poppler/XRef.cc   |2 +-
 qt4/src/Doxyfile  |2 +-
 qt5/src/Doxyfile  |2 +-
 qt5/src/poppler-private.h |1 +
 11 files changed, 24 insertions(+), 8 deletions(-)

New commits:
commit 478be219772a6c298baad568da3643895cd50d35
Author: Albert Astals Cid 
Date:   Fri Apr 21 16:29:44 2017 +0200

Poppler 0.54

diff --git a/CMakeLists.txt b/CMakeLists.txt
index f2ff0c0d..b3ff39de 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -22,7 +22,7 @@ if (ECM_FOUND)
 endif()
 
 set(POPPLER_MAJOR_VERSION "0")
-set(POPPLER_MINOR_VERSION "53")
+set(POPPLER_MINOR_VERSION "54")
 set(POPPLER_MICRO_VERSION "0")
 set(POPPLER_VERSION 
"${POPPLER_MAJOR_VERSION}.${POPPLER_MINOR_VERSION}.${POPPLER_MICRO_VERSION}")
 
diff --git a/NEWS b/NEWS
index 1cf43ce0..8f02c6e4 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,17 @@
+Release 0.54.0
+core:
+ * Make XRef reconstruction a bit better. Bug #100509
+
+glib:
+ * Expose movie play mode. Bug #99625
+ * demo: Show play mode in movie properties view
+
+qt5:
+ * Compile with -DQT_NO_CAST_FROM_BYTEARRAY. Bug #100311
+
+utils:
+ * pdfimages: don't fail listing if inline image data contains 'EI'. 
Bug #100737
+
 Release 0.53.0
 core:
  * Form support improvements
diff --git a/configure.ac b/configure.ac
index 7a233b9b..050a8912 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,5 +1,5 @@
 m4_define([poppler_version_major],[0])
-m4_define([poppler_version_minor],[53])
+m4_define([poppler_version_minor],[54])
 m4_define([poppler_version_micro],[0])
 
m4_define([poppler_version],[poppler_version_major.poppler_version_minor.poppler_version_micro])
 
diff --git a/cpp/Doxyfile b/cpp/Doxyfile
index e969a627..665af301 100644
--- a/cpp/Doxyfile
+++ b/cpp/Doxyfile
@@ -31,7 +31,7 @@ PROJECT_NAME   = "Poppler CPP"
 # This could be handy for archiving the generated documentation or
 # if some version control system is used.
 
-PROJECT_NUMBER = 0.53.0
+PROJECT_NUMBER = 0.54.0
 
 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
 # base path where the generated documentation will be put.
diff --git a/glib/CMakeLists.txt b/glib/CMakeLists.txt
index a40fc8ab..8433d2a3 100644
--- a/glib/CMakeLists.txt
+++ b/glib/CMakeLists.txt
@@ -81,7 +81,7 @@ set(poppler_glib_generated_SRCS
   ${CMAKE_SOURCE_DIR}/poppler/CairoRescaleBox.cc
 )
 add_library(poppler-glib SHARED ${poppler_glib_SRCS} 
${poppler_glib_generated_SRCS})
-set_target_properties(poppler-glib PROPERTIES VERSION 8.8.0 SOVERSION 8)
+set_target_properties(poppler-glib PROPERTIES VERSION 8.9.0 SOVERSION 8)
 target_link_libraries(poppler-glib poppler ${GLIB2_LIBRARIES} 
${CAIRO_LIBRARIES} ${FREETYPE_LIBRARIES})
 if(HAVE_PTHREAD)
target_link_libraries(poppler-glib -lpthread)
diff --git a/glib/Makefile.am b/glib/Makefile.am
index c2605cbf..1cae1229 100644
--- a/glib/Makefile.am
+++ b/glib/Makefile.am
@@ -82,7 +82,7 @@ libpoppler_glib_la_LIBADD =   \
$(FREETYPE_LIBS)
 
 libpoppler_glib_la_LDFLAGS =   \
-   -version-info 16:0:8\
+   -version-info 17:0:9\
@create_shared_lib@ \
@auto_import_flags@
 
diff --git a/gtk-doc.make b/gtk-doc.make
index e4a12a5b..2454c285 100644
--- a/gtk-doc.make
+++ b/gtk-doc.make
@@ -196,6 +196,7 @@ html-build.stamp: sgml.stamp $(DOC_MAIN_SGML_FILE) 
$(content_files) $(expand_con
  if test -f $(abs_builddir)/$$file ; then \
cp $(abs_builddir)/$$file $(abs_builddir)/html; \
  fi; \
+ test -f $$file && cp $$file $(abs_builddir)/html; \
done;
$(GTK_DOC_V_XREF)gtkdoc-fixxref --module=$(DOC_MODULE) 
--module-dir=html --html-dir=$(HTML_DIR) $(FIXXREF_OPTIONS)
$(AM_V_at)touch html-build.stamp
diff --git a/qt4/src/Doxyfile b/qt4/src/Doxyfile
index 04a12221..98d8f8d7 100644
--- a/qt4/src/Doxyfile
+++ b/qt4/src/Doxyfile
@@ -31,7 +31,7 @@ PROJECT_NAME   = "Poppler Qt4 "
 # This could be handy for archiving the generated documentation or
 # if some version control system is used.
 
-PROJECT_NUMBER = 0.53.0
+PROJECT_NUMBER = 0.54.0
 
 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
 # base path where the generated documentation will be put.
diff --git a/qt5/src/Doxyfile b/qt5/src/Doxyfile
index 0b4e3e51..1cd97d03 100644
--- a/qt5/src/Doxyfile
+++ b/qt5/src/Doxyfile
@@ -31,7 +31,7 @@ PROJECT_NAME   = "Poppler Qt5"
 # This could be handy for archiving the generated documentation or
 # if some version control system is used.
 
-PROJECT_NUMBER = 0.53.0

[poppler] Changes to 'refs/tags/poppler-0.54'

2017-04-21 Thread Albert Astals Cid 
Tag 'poppler-0.54' created by Albert Astals Cid  at 2017-04-21 
14:35 +

poppler 0.54

Changes since poppler-0.53-7:
---
 0 files changed
---
___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

Re: [poppler] Support for XMP metadata in poppler?

2017-04-21 Thread Albert Astals Cid 
El divendres, 21 d’abril de 2017, a les 1:05:34 CEST, jose.ali...@gmail.com va 
escriure:
> Hey List,
> 
> sorry if this has been discussed, but afaik, poppler does not read the XMP
> metadata when trying to find the title, or creation dates, etc. It's that
> corret. If so, is there is any reason why we don't have such suppport
> (other than nobody submitted a patch?) ... I tried to search in the list
> and the web but only found an old email saying that someone has submitted a
> patch to the list while ago (2007 or so)... So I am wondering about this.
> 
> Is the solution to read the metadata with another library? or shoud we add
> some logic in poppler to do this?

As far as I can see, we expose the "Metadata" catalog field, but just the XML 
blob.

You are suggesting to parse it directly, right?

The only "problem" with that is that if we do it on the core it means adding 
an extra dependency. 

Or you don't mean the "Metadata" catalog field?

Cheers,
  Albert

> 
> 
> Greetings
> 
> José


___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

Re: [poppler] Hello

2017-04-21 Thread Jason Crain 
On Fri, Apr 21, 2017 at 10:31:57AM +0200, Amila Fernando wrote:
> I want to know if poppler is just a pdf viewer or it's also an interpreter
> that I can use for the rip? If it's an interpreter I can use it? It's free
> or there is a commercial license to buy for it's use?

There is no commercial licensing.  Poppler is licensed under GPL
versions 2 or 3.  You are free to use it as long as you comply with the
GPL, which in short means that if you distribute the poppler software or
some product that includes the poppler software, you also have to share
the poppler source code, the source code of any modifications you make,
and the source code of any programs which use poppler, also licensed
under the GPL.  Read the GPL for more information.

I don't know what is needed for a RIP so I can't say whether it is
suitable for that purpose, but the poppler maintainer will consider any
patches you provide.
___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

Re: [poppler] Contributing to Poppler

2017-04-21 Thread Albert Astals Cid 
El dijous, 20 d’abril de 2017, a les 14:13:14 CEST, Simon Shugar va escriure:
> Hello,

Hi

> 
> I've just joined the group and would like to start contributing to Poppler.
> I am not sure how I should go about contributing to the project, is there
> any documentation or instructions for the process? 

Not really, just download the code, write any improvement/bugfix you want to 
make and send the patch.

We'll go on from there.

Do you have any specific thing you want to improve?

Cheers,
  Albert

> This will be the first
> time I have contributed to an open source project.
> 
> I am looking forward to working with you all.
> 
> Kind regards,
> Simon Lee Shugar
> 
> --
> 
> [image: Veeva Systems - Zinc Team]
> 
> *Simon Shugar*
> Software Engineer
> *Veeva Systems *
> simon.shu...@veeva.com
> www.veeva.com
> 
> *This email and the information it contains are intended for the intended
> recipient only, are confidential and may be privileged information exempt
> from disclosure by law.*
> *If you have received this email in error, please notify us immediately by
> reply email and delete this message from your computer.*
> *Please do not retain, copy or distribute this email.*


___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

Re: [poppler] Hello

2017-04-21 Thread Martin Schröder 
2017-04-21 10:31 GMT+02:00 Amila Fernando :
> I’m Amila Fernando. I’m a developer working at Grafco A.S.T.
>
> I never use poppler before. In our company we are considering to devolop a 
> RIP, so we are looking for modules that we can use. We are considering all 
> possibilities so,
>
> I want to know if poppler is just a pdf viewer or it’s also an interpreter 
> that I can use for the rip? If it’s an interpreter I can use it? It’s free or 
> there is a commercial license to buy for it’s use?

I'm seriously tempted to write a mail to your boss telling him to
invest in some Google training for you.
But I'm nice today: Read https://it.wikipedia.org/wiki/Poppler
___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

[poppler] Hello

2017-04-21 Thread Amila Fernando 
Hello,

 

I'm Amila Fernando. I'm a developer working at Grafco A.S.T. 

I never use poppler before. In our company we are considering to devolop a
RIP, so we are looking for modules that we can use. We are considering all
possibilities so,

I want to know if poppler is just a pdf viewer or it's also an interpreter
that I can use for the rip? If it's an interpreter I can use it? It's free
or there is a commercial license to buy for it's use?

 

Best Regards,   

Amila Fernando

 

 

 

 

 

 

 

 

cid:B3E361A3-7477-4BD9-ACF5-4B11AC45F711

 


Amila Fernando

 

 

GRAFCO AST s.r.l. 

 


Via del Lavoro 3
31050 Camalo di Povegliano
Treviso (TV) - Italy

 


VAT: IT04180370266




Tel.  : +39 0422 872241

 

Fax : +39 0422 872243

 

WEB :   www.grafcoast.com

 

E-Mail :   i...@grafcoast.com

 

  @Linkedin
 @twitter

 

 

___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler

Re: [poppler] evince does not show chinese bold or italic

2017-04-21 Thread William Bader 
atril (the Mate desktop version of evince, I think using poppler-0.34.0) on 
Fedora 23 gets the bold but not the italic.


pdftops-0.53.0 -level3 also gets the bold but not the italic.


pdftops-0.53.0 -level2 generates a ps that fails in ghostscript with Error: 
/rangecheck in --xyshow-- , possibly similar to 
https://bugs.freedesktop.org/show_bug.cgi?id=63963

It looks like the file does not contain the fonts.

$ pdffonts chinese_bold_italic.pdf
name type  encoding emb sub 
uni object ID
 -  --- --- 
--- -
STSong-Light CID TrueType  UniGB-UCS2-H no  no  
no   7  0
STSong-Light,BoldCID TrueType  UniGB-UCS2-H no  no  
no  10  0
STSong-Light,Italic  CID TrueType  UniGB-UCS2-H no  no  
no  13  0
STSong-Light,BoldItalic  CID TrueType  UniGB-UCS2-H no  no  
no  16  0


$ pdffonts -subst chinese_bold_italic.pdf
name object ID substitute font  
substitute font file
 - 
 
STSong-Light  7  0 Source Han Sans CN Light 
/usr/share/fonts/adobe-source-han-sans-cn/SourceHanSansCN-Light.otf
STSong-Light,Bold10  0 Source Han Sans CN Bold  
/usr/share/fonts/adobe-source-han-sans-cn/SourceHanSansCN-Bold.otf
STSong-Light,Italic  13  0 Source Han Sans CN Regular   
/usr/share/fonts/adobe-source-han-sans-cn/SourceHanSansCN-Regular.otf
STSong-Light,BoldItalic  16  0 Source Han Sans CN Bold  
/usr/share/fonts/adobe-source-han-sans-cn/SourceHanSansCN-Bold.otf


Regards, William


From: poppler  on behalf of Thomas 
Johnsson 
Sent: Thursday, April 20, 2017 11:28 AM
To: poppler@lists.freedesktop.org
Subject: [poppler] evince does not show chinese bold or italic

Now that Adobe has retracted support for Adobe Reader for Linux, we
use Evince as the default pdf viewer.
But we have an issue with evince for chinese text with bold, italic or both.
The font(s) used are "STSong-Light", "STSong-Light,Bold"  ,
"STSong-Light,Italic" , and "STSong-Light,BoldItalic" .

Attached screenshots show an example line with each of the fonts above,
displayed by (Adobe Acrobat Reader) acroread, and evince.
As can be seen, evince shows no difference between the lines of chinese
text.
I also attach the pdf file.
Latest tested evince version: 3.14.2 (RHEL7).

I suspect (but I'm not sure) that acroread synthesizes bold and italic
from the regular font, and that evince fails to do so.
Or could it be that additional fonts need to be installed?
Or might this have been fixed in a later version of evince?

Kind regards,
Thomas Johnsson



___
poppler mailing list
poppler@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler