World: r4wp

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

http://red.esperconsultancy.nl/Red-common/dir?ci=tip

http://red.esperconsultancy.nl/Red-common/timeline

Which issues?

Discussed elaborately above

Which were disagreements at what is advertised as working.

Eh, then why did Peter implement a lot of code for it?

Because that's code which is still missing, as Doc stated multiple 
times.

Yes, and it was "advertised" as you say as already implemented. But 
why are we discussing this over? We are working on fixing it

I didn't see any advertisement beyond the basic Red string! supporting 
Unicode. Doc stated multiple times that the external en/decoders 
are not yet in place for this to be of much use.

It was announced last year that Unicode support was implemented in 
a week. What I found first is that Unicode support is useless, and 
now I've found that only ASCII is really supported

But I'm tired of trying to convince people of it. I'll just go back 
to finishing what I need

If Unicode support wouldn't be implemented, Peter would have a very 
hard time writing those transcoders.

If you're happy with your definition of "support", I'll go back to 
implementing the support I need

Just a matter of discerning internal implementation details and user-visible 
external features.

Could we say that internal unicode support exists, but is not available 
for I/O?

Kaj: you're basically saying that all the Unicode tests we wrote 
in the tests suite are lying...which is obviously wrong.

Precisely, yes.

Yes, internal features are of no use to me. I want to write actual 
programs

Again, I'm tired of explaining this. Red can input some Unicode and 
print some Unicode. That's enough to support the test suite, but 
mostly useless in real life programs

More importantly, Red can internally _represent_ Unicode.

Writing actual programs: I would like too, but until I/O is not fully 
implemented in Red, we are limited into what can be done. That's 
why Red is in alpha state.

I'm not contesting that. I just want features to be represented truthfully, 
lest we get slaughtered on the public Internet

Agreed, if we have some misleading naming or feature not implemented 
as advertised, please report them with all the required details for 
me to process it, either here or on the bugtracker. But simply bashing 
Red won't help.

Please, I'm not bashing Red, I'm trying to represent it truthfully. 
I'm trying to protect it from getting bashed. Why would I bash a 
project I spent the last two years of my life on?

It's exactly that I sometimes get the feeling that you're not taking 
my observations seriously that I am afraid for this misrepresentation

I think this is just a misunderstanding. Kaj, would you be happy 
with a simple language change, for now, that descibes the current 
state of external unicode support?

Yes, I think it's very dangerous to claim that Red has Unicode and 
Latin-1 support

We could say they are supported internally, but I/O is TBD. But I'm 
all for a simple text change that solves this for now.

Well, the console Latin1 claim is wrong, other than that, there are 
no claims that Red supports Latin1.

Gregg: that's already what is claimed at the moment, but it seems 
to not be a very communicable message.

Kaj: I do take into account all observations, and especially from 
people that work on it and with it since the beginning. I just can't 
do miracles and implement in a night features that take weeks.

Where is the exact text in question?

I'm not asking that of you, and I'm working on it myself

So it's probably better to not mention Unicode at all, for now (which 
is what I understand Kaj suggesting).

I'm good with that. I'm American so I don't care about any of this. 
;-)

Not really. Mentioning internal features as such is fine. It's not 
even true that I/O is to be done, because I support it

Unicode support was claimed on Twitter

Finally had the chance to look over this:

For: print read 

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

Yes, syllable.org is UTF-8

Looks like the newer Beagleboards are using regular ARM CPU (no more 
Cortex-M series), so Red should run just fine on them:

http://techcrunch.com/2013/04/23/the-beaglebone-black-is-a-new-single-board-computer-that-can-brew-beer/

Thanks Doc, I might go ahead and create that group and just do repost 
on RED status updates via Linked in as new news is posted.  Does 
RED have an "official Logo" yet?

Nope, as we haven't found someone skilled enough yet to convert the 
Tower of HanoÏ draft into a real logo.

You can use the one I'm using for #red_lang on Twitter.

I'd like to know what your development environment for Red/System 
is especially that used by Doc.
In the meantime...
	My development environment:
	OS: Windows 7
	Editor: Notepad++ v5.0.3
	  not the latest version but I prefer this one,

   using "Python" as the language for syntax highlithing and coloring

   (there is not a "REBOL" language) and used mainly for the folding 
   on indentation

   (I can not live without folding, and folding on indentation makes 
   life even easier)

   I have added a menu item with a keybord shortcut to run REBOL with 
   the currently shown file as argument.

   I have added also a menu item with a keybord shortcut to run my modified 
   version of REBOL-Word-Browser

 At the end of the r/s file I add these lines (mostly taken from Bruno 
 Anselme):
		#if OS = '???? [{
		REBOL []
		appname: "myprog"

  rs-dir: %../Red-master-0.3.2_Bruno/red-system                ; locate 
  here your red-system directory
		dest: rejoin [what-dir appname ]
		print [ "------ Compiling" appname "------" ]
		do/args rs-dir/rsc.r rejoin ["-o " dest " " dest %.reds ]

		print [ "Destination file:" dest ]
		call/wait/show/console dest
		halt
		;}]

 This way pressing the shortcut I can run REBOL that compiles the 
 program I am writing and than starts the program.
	Any suggestion is welcomed!

Nice way to get self-compiled Red/System scripts. :-)

I use Textpad on Win7 for coding. As Textpad does not support Unicode, 
I also use Notepad++ for Red UTF-8 scripts. On Windows, I use PE 
Explorer for reviewing the disassembled code and IDA Pro for debugging 
it (hopefully, this happens rarely). I also use IDA Pro on Linux/IA-32 
and gdb everywhere else. On Mac, I try to use osxdebug, when it's 
not crashing.


I dream about the day when I'll be able to replace all those tools 
with a cross-platform Red[/System] IDE.