World: r4wp

I found out that not only does Red not support Unicode, it doesn't 
support Latin-1, not even on Windows

Both the compile time and runtime lexers don't let Latin-1 through

I've relabeled my console versions as supporting only ASCII

Hey guys was just thinking.  Why not a RED group on linkedin.com? 
 Doc you should start one up.  I'll definatley join and think many 
here would.  Would be another outlet to get more discussion with 
those outside of the usual outlets.

Good idea. I would join from the start. But better maybe in a later 
stage of the development? When it is more appropriate to attrackt 
more outside momentum because there is even more Red to show to the 
world? After Red becomes really selfsupporting? It seems to me all 
the other channels are taking a lot of time for Nenad as is.

It's low maintemance - more a badge of recognition for the time being 
but since Doc updates the red-lang.lorg site may just as well put 
those posts in the linked group also.

I don't use it, but isn't it more for business networking? Not saying 
it would be bad to show that people use Red (when that time comes), 
but I don't know how appropriate it would be for language discussion.

If Doc needs to do updates another place, that's not good, as we 
need to help keep him focused. If someone else is responsible, that 
would be best.

What we need is more activity on Facebook as well. Just look when 
last message was posted. Ppl are grateful for any kind of news ....

Gregg: +1

Paul: feel free to open one and send us invitations, but I personaly 
have no time to post news on yet another channel  (I already post 
here, on Twitter and on red-lang.org, and answer questions on IRC, 
SO chat, ...)

Pekr: I think FB was a mistake, it's not the right place/tool where 
to have technical discussions (especially on deep topic like programming 
languages).

Kaj: I don't understand what you are talking about. If you cared 
about giving an example or any useful information I could look at 
or work on, your post would look a bit more constructive.

I've been working on adding UTF-8 support for the past week, so you'll 
see construction soon

Here's what happens when I paste UTF-8 in the console on Linux:

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

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

A very similar thing happens when I paste Latin-1 into Windows

Here's what happens when I try to compile Latin-1 source code:

-= Red Compiler =- 
Compiling /home/kaj/Red/common/examples/Latin-1.red ...
*** Syntax Error: Invalid string! value
*** line: 5
*** at: {"Espa\ufffdol.txt" "Espa\ufffdol"^M
}

Compiling: 
	Red [ ] print s: "Español"
works fine here and prints the correct output when run.

Red input sources must be UTF-8 encoded.

You can't paste UTF-8 in the console, it supports only Latin-1.

Yes, so the Latin-1 promise is false

??

You can't paste Latin-1

Are you sure you're pasting Latin-1 and not UTF-8?

Yes, tried many times many ways

The printing backend doesn't fully support Unicode, either. This 
works on Linux:

print read "http://syllable.org"

But on Windows the output is truncated somewhere between the Spanish 
and Russian text parts

Does READ create a red-string!?

Yes

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

string/load can only load UTF-8, so only ASCII and UTF-8 files can 
be read, not Latin-1

You caught me while in the middle of work on pic-emitter, I switched 
to master branch without saving my changes, and now my local git 
repo is messed up (not sure why it happened). I can't test anything 
anymore before finding a way to fix it...

Kaj, are you anyhow pressed for time with your solution? I can smell 
some push here, and Doc is now working on another priority. I would 
let him finish pic emitter and then ask for eventual rescheduling 
of priorities ...

I've just fixed my repo with the help of Andreas.

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