OK, I committed the following in Zn #bleedingEdge:
===
Name: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.46
Author: SvenVanCaekenberghe
Time: 7 February 2017, 11:07:31.306364 am
UUID: a2928299-1dda-4fdf-b15e-e5d7bed2373e
Ancestors: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.45
Add
> On 6 Feb 2017, at 22:33, Nicolai Hess wrote:
>
>
>
> 2017-02-04 13:40 GMT+01:00 Sven Van Caekenberghe :
>
> > On 4 Feb 2017, at 13:01, Nicolai Hess wrote:
> >
> >
> >
> > 2017-02-04 12:49 GMT+01:00 Sven Van Caekenberghe
2017-02-04 13:40 GMT+01:00 Sven Van Caekenberghe :
>
> > On 4 Feb 2017, at 13:01, Nicolai Hess wrote:
> >
> >
> >
> > 2017-02-04 12:49 GMT+01:00 Sven Van Caekenberghe :
> > Hi Nicolai,
> >
> > The FileSystem API is a bit inconsistent, yes.
> >
>
> On 4 Feb 2017, at 21:14, stepharong wrote:
>
> I will talk about guille about his file implementation and we can see what we
> can do.
Yes, that is step 1, here is the issue I was talking about:
I will talk about guille about his file implementation and we can see what
we can do.
On Sat, 04 Feb 2017 20:28:07 +0100, Denis Kudriashov
wrote:
2017-02-04 19:09 GMT+01:00 stepharong :
Sven
I really think that we should clean and improve on
Guilermo's new File class with its simple binary streams can be
perfectly combined (stacked) with Zn character encoding streams. A first
step would be to make FileSystem return/produce those stacked streams.
I even believe there is a prototype integrating this
I believe you are one (the
2017-02-04 19:09 GMT+01:00 stepharong :
> Sven
>
> I really think that we should clean and improve on this side.
> What would be a roadmap?
>
> - Improve filesystem API to call Zn
> - Deprecated other users? (what are they?)
> - what would be the next steps?
Yes, we need
> On 4 Feb 2017, at 19:09, stepharong wrote:
>
>
>>> 2017-02-04 12:49 GMT+01:00 Sven Van Caekenberghe :
>>> Hi Nicolai,
>>>
>>> The FileSystem API is a bit inconsistent, yes.
>>>
>>> This is how you can use it:
>>>
>>> (FileLocator temp / 'foo.txt')
Le 04/02/2017 à 19:09, stepharong a écrit :
2017-02-04 12:49 GMT+01:00 Sven Van Caekenberghe :
Hi Nicolai,
The FileSystem API is a bit inconsistent, yes.
This is how you can use it:
(FileLocator temp / 'foo.txt') writeStreamDo: [ :out |
out binary.
(ZnCharacterWriteStream
2017-02-04 12:49 GMT+01:00 Sven Van Caekenberghe :
Hi Nicolai,
The FileSystem API is a bit inconsistent, yes.
This is how you can use it:
(FileLocator temp / 'foo.txt') writeStreamDo: [ :out |
out binary.
(ZnCharacterWriteStream on: out encoding: #utf8) << 'élève' ].
> On 4 Feb 2017, at 13:01, Nicolai Hess wrote:
>
>
>
> 2017-02-04 12:49 GMT+01:00 Sven Van Caekenberghe :
> Hi Nicolai,
>
> The FileSystem API is a bit inconsistent, yes.
>
> This is how you can use it:
>
> (FileLocator temp / 'foo.txt') writeStreamDo:
Hi Nicolai,
The FileSystem API is a bit inconsistent, yes.
This is how you can use it:
(FileLocator temp / 'foo.txt') writeStreamDo: [ :out |
out binary.
(ZnCharacterWriteStream on: out encoding: #utf8) << 'élève' ].
(FileLocator temp / 'foo.txt') readStreamDo: [ :in |
in binary.
Hi
How can I specify the character encoding when opening a readStream on a
FileRerefence.
I found this, that works:
| readStream fileContent |
readStream := (File named: aFileName) openForRead.
fileContent := ZnCharacterReadStream on: readStream encoding: encoding.
fileContent upToEnd asString.
13 matches
Mail list logo