Re: [Podofo-users] Could someone tell me the encode type of HexString followed by Tj

[Matthew Brincke via Podofo-users]

On Tuesday, 12.04.2022 at 18:34 +0800 Alex wrote:
> Hi,
> 
>     When I opened a pdf file using podofobrowser.exe,if a pdfobject
> has a stream object,podofobrowser.exe will show the content of the
> stream as the following:
> 
> 
> BT
> /F2 10.56 Tf
> 1 0 0 1 136.46 758.28 Tm
> 0 g
> 0 G
> [(pdf)] TJ
> ET
> 
> BT
> /F1 10.56 Tf
> 1 0 0 1 154.94 758.28 Tm
> 0 g
> 0 G
> [<08CF372D>] TJ
> ET
> 
> 
> In the first BT object,I know easily the text string is “pdf “ by
> ([(pdf)] TJ),but it is difficult to understand [<08CF372D>] TJ in the
> second BT object,could someone tell me how to understand
> [<08CF372D>], what encode type is this.

Hi Alex,

the text is given as a HexString (correct), but the encoding of it
is given by the encoding of the font referenced as the name /F1 in
your PDF snippet (operator Tf). So if you'd like more information,
I'd need the content of the PDF object whose reference is given
after the name /F1 in the /Font property of your PDF's /ProcSet,
and also the contents of the objects whose references are given
after /Encoding and /FontDescriptor in that object (long arrays can 
be abbreviated). Thanks in advance. Pleased to read from you again.
                                                                     
>                              Thanks,
>                                                                      
>                                 Alex
> 

Best regards, mabri

___
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users

Re: [Podofo-users] [RFC] pdfmm 0.9.20 released and offer to merge back to PoDoFo

[Matthew Brincke via Podofo-users]

On Friday, 08.04.2022 at 15:38 +0200 Dominik Seichter via Podofo-users
wrote:
> Hi Zyx, Hi Francesco,

Hi Dominik, hi zyx, hi Francesco,
> 
> I also wanted to continue this discussion. Sorry again for the long
> delay. If you prefer, we could also have a phone/video chat
> about these points (also whoever is interested could join in).

firstly, I'm sorry for not posting for so long, I had so much to do IRL
in the meantime. As there seem to be times of change ahead for PoDoFo,
I'd like to assume an active role in the project again.
> 
> From my point of view, the most important points/next steps are as
> follows (feel free to correct me if I am wrong):
> 
> 1) Decision on splitting PoDoFo and PoDoFo Tools: 
> I would prefer to keep them in the same repository to make sure they
> are in a buildable state all the time and can also be used as
> examples for working with PoDoFo.

Seconded.

> @Francesco Pretto : It would be great if you could take the
> additional effort and port them to pdfmm. The diff could also be a
> nice migration guideline for the future.
> 
> 2) Decision on license of PoDoFo Tools: 
> PoDoFo Tools are currently GPL whereas the library itself is LGPL.
> This e.g. makes it hard to copy from tools to the library. From my
> point of view, we should align the license so that the tools have the
> same license as the library (currently LGPL, for the future see
> separate discussion).

I always understood this difference as having a purpose
(in my view, warning people off taking PoDoFo tools and making
something non-free out of them).
> 
> 3) Merging back pdfmm in podofo / replacing podofo with pdfmm:
> I would agree to the proposal from Francesco here. We should do one
> last release of PoDoFo 0.9.8 based on the current svn trunk and then
> replace it. 
> @Zyx: When would be a good point of time for this? Can I just bundle
> a trunk, do quick tests and upload it? I am not sure about the
> current state.

Especially @Dominik: IIRC (I've lurked here in the meantime and looked
in the issue tracker on SourceForge a few times),
there are some patches still outstanding which I'd like to test (using
some "poor man's CI/test automation" locally most likely)
and then apply to SVN trunk, which fix security issues/crashers, so
that I'd be grateful for considering them
necessary for the next release. I'm not currently doing other work (a
day job), so I think I can do this quickly,
I hope starting tomorrow (Sunday). For the other issues labeled
"security" I'd also like to see what I can do
(I hope to produce patches and then handle them like the others, could
you please do too?).
> 
> 4) Move to Git: 
> Yes, let's move to Git* and keep website, mailing list on
> sourceforge.

Yes (after next release, I hope, if I'll succeed in committing with my
mabri SourceForge user account).
Issues which won't be copied to the new version control hosting (to
enable further work on them, after the move,
if the new issue tracker also has such features as e.g. issue states,
besides open/closed, the SourceForge one has)
should be closed at SourceForge, of course (IMHO at least).
> 
> 5) relicensing to MPL:
> I am in general open to that, but let's keep discussion in separate
> mail thread.

I think I'd like to think/discuss more about that (at least it's
copyleft?), in its mail thread.
> 
> 
> Best regards,
>  Dominik

Best regards, mabri
> 
> 
> 
> 
> On Tue, Feb 22, 2022 at 9:39 AM zyx  wrote:
> > On Mon, 2022-02-21 at 12:17 +0100, Francesco Pretto wrote:
> > > Please understand that after the port I would still need to
> > "recruit"
> > > people to ensure they actually work as intended. In short words:
> > they
> > > need a maintainer who cares about them.
> > 
> >         Hi,
> > sure, that's fine. As far as I can tell, it's no change from the
> > current state.
> >         Bye,
> >         zyx
> > 
> > 
> > ___
> > Podofo-users mailing list
> > Podofo-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/podofo-users
> ___
> Podofo-users mailing list
> Podofo-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/podofo-users

___
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users

Re: [Podofo-users] Questions about Support Model Podofo A2308KMA3AM1EU

[Matthew Brincke via Podofo-users]

Hello Mr. Reuter,

this mailing list is of libpodofo, a software programming library and
associated software tools/examples for working with Portable Document
Format files/data (therefore its name from the first two characters of
each word written initial-capitalized) and has nothing to do with
hardware. Your inquiry/complaint is therefore sent to a venue where
questions about hardware (unless you can show it uses libpodofo) are
off-topic (it is not for those). Please continue your search for a
support forum or customer service venue elsewhere.

Best regards,

Matthew B.

On 05.03.22 at 12:33 wrote wolreu--- via Podofo-users:
>
>  
>
>  
>
> Gesendet von Mail  für
> Windows
>
> Greetings,
>
>  
>
> i bought this Podofo A2308KMA3AM1EU and by installing the device some
>
> things i missed or no function.
>
>  
>
>
___
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users