Re: [Pharo-users] Artefact and WideString

On 22-10-15 16:16, Sven Van Caekenberghe wrote: Most but not all use 128 as encoding. But Latin1 is not one of them (at least not in the strict interpretation). Hmm, you can't trust anything you read on the internet anymore:) CP1252, legacy Windows it is. Stephan

Re: [Pharo-users] Artefact and WideString

> On 22 Oct 2015, at 16:00, Stephan Eggermont wrote: > > On 22/10/15 12:01, Sven Van Caekenberghe wrote: >> >>> On 22 Oct 2015, at 11:14, Hilaire wrote: >>> >>> Le 21/10/2015 22:26, olivier auverlot a écrit : Hi Hilaire, Take a look in the Artefact demos. I think there are a P

Re: [Pharo-users] Artefact and WideString

> On 22 Oct 2015, at 3:31 , Sabine Manaa wrote: > > I do also use two different implementations for artefact/pdf and html: > > artefact: > 128 asCharacter asString > > html: > '€' > > same would be great https://www.adobe.com/content/dam/Adobe/en/devnet/pdf/pdfs/PDF32000_2008.pdf

Re: [Pharo-users] Artefact and WideString

On 22/10/15 12:01, Sven Van Caekenberghe wrote: On 22 Oct 2015, at 11:14, Hilaire wrote: Le 21/10/2015 22:26, olivier auverlot a écrit : Hi Hilaire, Take a look in the Artefact demos. I think there are a PDF document with a monetary character. Indeed ((128 asCharacter) asString). I am

Re: [Pharo-users] Artefact and WideString

> On 22 Oct 2015, at 15:31, Sabine Manaa wrote: > > I do also use two different implementations for artefact/pdf and html: > > artefact: > 128 asCharacter asString I am still very curious to know in which character encoding that is the case ? https://en.wikipedia.org/wiki/Currency_sign_(typo

Re: [Pharo-users] Artefact and WideString

I do also use two different implementations for artefact/pdf and html: artefact: 128 asCharacter asString html: '€' same would be great 2015-10-22 15:11 GMT+02:00 HilaireFernandes [via Smalltalk] < ml-node+s1294792n485732...@n4.nabble.com>: > Le 22/10/2015 12:01, Sven Van Caekenberghe a écr

Re: [Pharo-users] Artefact and WideString

Le 22/10/2015 12:01, Sven Van Caekenberghe a écrit : > I am pretty sure this is wrong. The Unicode code point for the Euro symbol is > decimal 8364 and not 128. > > https://en.wikipedia.org/wiki/Euro_sign Indeed. I guess the 128 value is for 8 bits char encoding, and it is the one required by Arte

Re: [Pharo-users] Artefact and WideString

> On 22 Oct 2015, at 11:14, Hilaire wrote: > > Le 21/10/2015 22:26, olivier auverlot a écrit : >> Hi Hilaire, >> >> Take a look in the Artefact demos. I think there are a PDF document >> with a monetary character. >> > > Indeed ((128 asCharacter) asString). I am pretty sure this is wrong. Th

Re: [Pharo-users] Artefact and WideString

Le 21/10/2015 22:26, olivier auverlot a écrit : > Hi Hilaire, > > Take a look in the Artefact demos. I think there are a PDF document > with a monetary character. > Indeed ((128 asCharacter) asString). But this character does not print on the web with Unicode encoding. Unified support will be grea

Re: [Pharo-users] Artefact and WideString

Hi Hilaire, Take a look in the Artefact demos. I think there are a PDF document with a monetary character. 2015-10-21 22:02 GMT+02:00 Hilaire : > Hello, > > Is it me, or is there a problem with WideString and Artefact? > > The following produces an empty page: > > page add: ((PDFFormattedTextEl

[Pharo-users] Artefact and WideString

Hello, Is it me, or is there a problem with WideString and Artefact? The following produces an empty page: page add: ((PDFFormattedTextElement from: 10mm @ 20mm to: 277mm @ 30mm) alignment: PDFAlignment left; text: 'Argent de poche : 1€'). The text is WideString. Removing the €, it