World: r4wp

Kaj: I think you're right about the console, it handles correcty 
only ASCII input.

For: print read "http://syllable.org", do you feed string/load with 
an UTF-8 input even on Windows?

With the only function in Red that supports Unicode: string/load

 Red string! is fully supporting Unicode. Your issue is related to 
 I/O and Red has no support for that yet (except for the currently 
 hardwired stdout).

Doc, would you mind, if I would, from time to time, republish some 
of your tweets or other stuff on FB channel? I can still believe 
it has some value, maybe I am just used to the FB ...

Franckly, I've reached my limit wrt to communication channels. Also 
it would be counter-productive to me to do such tasks, I see no reason 
why it couldn't be done by someone else?

I think having comm lieutentants is a good idea.

Yes, that would be helpful.

OK, I'm on it :-)

Petr, I'm not pressed for time, except for my career in general. 
I only posted examples because Doc asked for them

I'm only pushing in so far as I have been inquiring about encoding 
support for several weeks, and the state of things has been downplayed, 
so I want it to be noted

Further, I'm working Unicode conversions directly into my I/O routines, 
so I need to know how Red currently functions and what the future 
plan is

ok, fair enough. I believe that Doc would wish Red development would 
go faster, but there's only 24 hourse per day, we know :-)

For example, there's an internal single byte encoding that's marked 
"Latin1", but I now know there is no way to get Latin-1 data in or 
out, so I wonder if this encoding will ever be used for more than 
7-bit ASCII

Yes, that's why I've been helping with the coding for over two years

yes, and as a contributor, you have been surely noticed :-) I am 
still somehow satisfied with how Red development goes, eg. even in 
comparison with R3. Nothing against R3, I wish Cyphre takes us to 
Android, but for general purpose needs, untill R3 gets protocols, 
multiline console, etc, stuff noticed on SO, it is no go for me. 
So, I keep my fingers crossed as far as Red development goes - it 
is nice to have a strong leader around ...

I'd better not comment on the Git issue, because it will be considered 
unconstructive :-)

Especially as it had nothing to do with Git, yes.

See?

As far as I understood the plan, the internal "Latin 1" encoding 
is used to store Unicode codepoints 0-255. So this should be used 
already.

Kaj: why don't you open a ticket with a code example on github if 
something is broken or not working as advertised? I thought that 
was our process to get issues solved.

Andreas: that's what is supposed to be implemented, but now I have 
a doubt about it. Will need to check the code tomorrow.

Because you said it's not a priority and because I'm trying to ananlyse 
and fix things myself first. I'm just reporting my findings

Actually, I did one test that confirms Andreas' statement. The only 
way to get 8-bit data in is to compile a UTF-8 string literal that 
fits into Latin-1

Sounds like it works as advertised, then.

No, the console says you can input Latin-1, and you can't, not even 
through UTF-8

Neither can you compile Latin-1 nor read Latin-1 files nor other 
source data

I didn't see the latter claimed anywhere.

See above

Labelling the internal storage format "Latin 1" may be slightly misleading, 
though.

-=== Red Console alpha version ===-
(only Latin-1 input supported)

red>> s: "Español"
== "Espa"
red>> length? s
== 4

Console and compilation are two separate things.

I didn't see a claim anywhere, that you can compile Latin 1 sources.

Yes, and neither works, so there is no Latin-1 support at all, except 
in a corner case internally

The "internal corner case" is no Latin1 support either. It's purely 
Unicode support, with a more efficient internal storage.

If Kaj is top Red user, maybe the priorities could be adjusted then? 
Depends on Doc, though ...

Yes, and as you say, it's mislabeled Latin1, so there were several 
thing leading me to believe that Red already had Unicode and Latin-1 
support

I don't say that it is mislabeled, I say that it might be misleading.

Indeed, it it misleads me, I don't see why not everyone would fall 
over Red if we present it to the public

But if you all would prefer me not inform you of my findings, perhaps 
I should go back to working in silence?

Didn't say anything to that effect, and it's not what I'm thinking 
either.

So the claim that the console supports Latin1 seems to be incorrect.

Yes, that's why I reported relabeling my console versions

Let's give Doc a couple days to recover from pic-emitter, and I'm 
sure he'll clarify things.

Other than that incorrect claim, there's no Latin1 support in Red 
whatsoever.

Exactly

These issues are all important to know about, but it's easy to misread 
intent in text.

I think we're all on the same page, if not the same code page.

So for most purposes, Red is currently ASCII only

Well, Unicode is still working as advertised.

No, I've reported those issues the weeks before, and I'm working 
on fixing some of them, after Peter's work