Yes please go ahead. One of these days I will have a look at the templating because with cocoon I have made a prototype based look up that can be applied instead of having one. Stef On Mon, Sep 11, 2017 at 9:17 PM, olivier auverlot <olivier.auverlot@gmail.com> wrote:

Hi Alejandro,

There are no activities in the Artefact project because it does what we need. Of course, if you want explore the world of Unicode, you can do it. We are interested :)

Best regards Olivier

2017-09-11 21:09 GMT+02:00 Cyril Ferlicot D. <cyril.ferlicot@gmail.com>:

...

Le 11/09/2017 à 21:03, Alejandro Infante a écrit :

...

Hi! I would like to explore having support for Unicode characters. I want to help for it.

Who is the right person to talk about it?

Hi,

Artefact was originally created by Guillaume Larcheveque and Olivier Auverlot. But I don't know if they have time to maintain it.

...

Cheers! Alejandro

-- Cyril Ferlicot https://ferlicot.fr

http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France

Looks like a worthwhile exercise PDFTalk https://wiki.pdftalk.de/doku.php "The syntax is covered comprehensively, which means that any PDF file can be read and any PDF object can be written in a conforming way. Typical PDF objects are dictionaries of which many are specialized as Smalltalk objects. The library code is annotated with the original descriptions and definitions from the specification, so that learning about PDF itself is well supported. " I wonder what the main issues would be when porting this to Pharo. --Hannes On 9/12/17, Denis Kudriashov <dionisiydk@gmail.com> wrote:

There is also PDFTalk from Christian Haider https://wiki.pdftalk.de/doku.php. But it needs to be ported into Pharo.

2017-09-11 21:03 GMT+02:00 Alejandro Infante <alejandroinfante91@gmail.com>:

...

Hi! I would like to explore having support for Unicode characters. I want to help for it.

Who is the right person to talk about it?

Cheers! Alejandro

Moin, the port is almost done. Then I will add documentation and publish the code under MIT licence. Including the code used to port the library from VW to Gemstone using a novel approach. The heard of the “PDF engine” is the type system which allows the assignment of Smalltalk classes to raw PDF objects. In the new version, the PDF types are decoupled from the Smalltalk classes, so that classes can be renamed freely (i.e. adding prefixes). I think that porting the new version to Pharo (and VA and …) has gotten much easier. I hope that someone would take the challenge :). Cheers, Christian Von: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] Im Auftrag von Denis Kudriashov Gesendet: Dienstag, 12. September 2017 11:12 An: Any question about pharo is welcome <pharo-users@lists.pharo.org> Betreff: Re: [Pharo-users] Who is maintaining of Artefact? Look at slides PDFtalk for Gemstone <https://www.slideshare.net/esug/pdftalk-for-gemstone> from last ESUG about porting it to Gemstone (which is done). Maybe it is similar as porting GLORP into Pharo. Somebody can comment on this process. 2017-09-12 11:04 GMT+02:00 H. Hirzel <hannes.hirzel@gmail.com <mailto:hannes.hirzel@gmail.com> >: Looks like a worthwhile exercise PDFTalk https://wiki.pdftalk.de/doku.php "The syntax is covered comprehensively, which means that any PDF file can be read and any PDF object can be written in a conforming way. Typical PDF objects are dictionaries of which many are specialized as Smalltalk objects. The library code is annotated with the original descriptions and definitions from the specification, so that learning about PDF itself is well supported. " I wonder what the main issues would be when porting this to Pharo. --Hannes On 9/12/17, Denis Kudriashov <dionisiydk@gmail.com <mailto:dionisiydk@gmail.com> > wrote:

There is also PDFTalk from Christian Haider https://wiki.pdftalk.de/doku.php. But it needs to be ported into Pharo.

2017-09-11 21:03 GMT+02:00 Alejandro Infante <alejandroinfante91@gmail.com <mailto:alejandroinfante91@gmail.com> >:

...

Hi! I would like to explore having support for Unicode characters. I want to help for it.

Who is the right person to talk about it?

Cheers! Alejandro

Von: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] Im Auftrag von Denis Kudriashov Gesendet: Dienstag, 12. September 2017 11:43 An: Any question about pharo is welcome <pharo-users@lists.pharo.org> Betreff: Re: [Pharo-users] Who is maintaining of Artefact? Hi Christian. 2017-09-12 11:38 GMT+02:00 Christian Haider <christian.haider@smalltalked-visuals.com <mailto:christian.haider@smalltalked-visuals.com> >: Moin, the port is almost done. Then I will add documentation and publish the code under MIT licence. Cool. And code repo is not public yet? No, still in private store. I will publish it to Cincom’s public store when I am ready. If you want to have a look, I could tell you privately where my store is… Including the code used to port the library from VW to Gemstone using a novel approach. The heard of the “PDF engine” is the type system which allows the assignment of Smalltalk classes to raw PDF objects. In the new version, the PDF types are decoupled from the Smalltalk classes, so that classes can be renamed freely (i.e. adding prefixes). I think that porting the new version to Pharo (and VA and …) has gotten much easier. I hope that someone would take the challenge :). Definitely Cheers, Christian Von: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org> ] Im Auftrag von Denis Kudriashov Gesendet: Dienstag, 12. September 2017 11:12 An: Any question about pharo is welcome <pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org> > Betreff: Re: [Pharo-users] Who is maintaining of Artefact? Look at slides PDFtalk for Gemstone <https://www.slideshare.net/esug/pdftalk-for-gemstone> from last ESUG about porting it to Gemstone (which is done). Maybe it is similar as porting GLORP into Pharo. Somebody can comment on this process. 2017-09-12 11:04 GMT+02:00 H. Hirzel <hannes.hirzel@gmail.com <mailto:hannes.hirzel@gmail.com> >: Looks like a worthwhile exercise PDFTalk https://wiki.pdftalk.de/doku.php "The syntax is covered comprehensively, which means that any PDF file can be read and any PDF object can be written in a conforming way. Typical PDF objects are dictionaries of which many are specialized as Smalltalk objects. The library code is annotated with the original descriptions and definitions from the specification, so that learning about PDF itself is well supported. " I wonder what the main issues would be when porting this to Pharo. --Hannes On 9/12/17, Denis Kudriashov <dionisiydk@gmail.com <mailto:dionisiydk@gmail.com> > wrote:

There is also PDFTalk from Christian Haider https://wiki.pdftalk.de/doku.php. But it needs to be ported into Pharo.

2017-09-11 21:03 GMT+02:00 Alejandro Infante <alejandroinfante91@gmail.com <mailto:alejandroinfante91@gmail.com> >:

...

Hi! I would like to explore having support for Unicode characters. I want to help for it.

Who is the right person to talk about it?

Cheers! Alejandro

On Tue, Sep 12, 2017 at 5:38 PM, Christian Haider < christian.haider@smalltalked-visuals.com> wrote:

Moin,

the port is almost done. Then I will add documentation and publish the code under MIT licence.

Including the code used to port the library from VW to Gemstone using a novel approach.

The heard of the “PDF engine” is the type system which allows the assignment of Smalltalk classes to raw PDF objects.

In the new version, the PDF types are decoupled from the Smalltalk classes, so that classes can be renamed freely (i.e. adding prefixes).

Thats great news Christian. Pharo's lack of namespaces and your desire to avoid prefixing classes made me wonder how to keep VW and Pharo ports synchronised - which added friction to my minor attempt to port it to Pharo.

I think that porting the new version to Pharo (and VA and …) has gotten much easier.

I hope that someone would take the challenge J.

I'm busy with other things for a while, but I'll add it back on my list of things to look at. cheers -ben

Cheers,

Christian

*Von:* Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] *Im Auftrag von *Denis Kudriashov *Gesendet:* Dienstag, 12. September 2017 11:12 *An:* Any question about pharo is welcome <pharo-users@lists.pharo.org> *Betreff:* Re: [Pharo-users] Who is maintaining of Artefact?

Look at slides PDFtalk for Gemstone <https://www.slideshare.net/esug/pdftalk-for-gemstone> from last ESUG about porting it to Gemstone (which is done).

Maybe it is similar as porting GLORP into Pharo. Somebody can comment on this process.

2017-09-12 11:04 GMT+02:00 H. Hirzel <hannes.hirzel@gmail.com>:

Looks like a worthwhile exercise

PDFTalk https://wiki.pdftalk.de/doku.php

"The syntax is covered comprehensively, which means that any PDF file can be read and any PDF object can be written in a conforming way.

Typical PDF objects are dictionaries of which many are specialized as Smalltalk objects.

The library code is annotated with the original descriptions and definitions from the specification, so that learning about PDF itself is well supported. "

I wonder what the main issues would be when porting this to Pharo.

--Hannes

On 9/12/17, Denis Kudriashov <dionisiydk@gmail.com> wrote:

...

There is also PDFTalk from Christian Haider https://wiki.pdftalk.de/doku.php. But it needs to be ported into Pharo.

2017-09-11 21:03 GMT+02:00 Alejandro Infante <alejandroinfante91@gmail.com>:

...

Hi! I would like to explore having support for Unicode characters. I want to help for it.

Who is the right person to talk about it?

Cheers! Alejandro

von Stephan Eggermont

On 12-09-17 11:11, Denis Kudriashov wrote:

...

Maybe it is similar as porting GLORP into Pharo. Somebody can comment on this process.

The important point is that the original code is in another dialect, and the idea is not to fork, as the original maintainer develops it further. That means that it is not a one-time translation, but is a set of transformation rules and platform specific packages that is applied every time something changes on either side.

Stefan, you are good :-)! Exactly! The full code transformation from VW to GS is described as a value, which gets interpreted by a generic code fileout machine. A new version of the GS fileout can be generated at any time without human intervention. A SystemChange (the name of the value class) could be interpreted in different ways. Currently, the transform is one way from VW to GS. I am very interested in changes people may do to the library, but for now, I will keep the master in VW and integrate contributions by hand. I am sure that, if the need arises, there will be a way to deal with a two-way synchronization. But let's have a contribution first :-) Christian