36 replies to this topic

[Cranium]

Last I've heard of it, it would require some updating of the resources for each and every character, but I can't remember. If you see, this topic is almost a year old. It's been a while. We'd have to wait for official dev input to see what would be needed to change this, although I'm thinking it might be possible now that mods are done differently with 1.6

[Anavrins]

I greatly approve of this suggestion, that would make of some use for all of those unused ascii characters!

[Zudo]

I support this!

[Sebra]

Cloudy, on 18 October 2012 - 08:42 AM, said:

...all the language support minecraft has is planned in ComputerCraft - which goes way beyond font.png.

I hope CC would not change behavior based on language settings in MC or else different players would see different results.
Unicode use several bytes per char even for latin letters, which is not good.
Ability to change font on device would help to use any wanted letters and icons, but it seems developers do not want it.

Also I see "åäö" if I did not switch to english even I have no such letters on my keyboard. On CC computer second letter also break input. Is it possible to get right input from windows, which knows installed language on client side?

[Hawk777]

Well, personally I would prefer CC to get proper Unicode support (even if only on the terminal, even if strings are still considered byte sequences rather than character sequences, since that’s a core Lua thing). Then we could have all the accents we want, and the line- and box-drawing characters.

[immibis]

Doesn't LuaJ mess up characters over 127?

[Hawk777]

immibis, on 15 September 2013 - 06:07 PM, said:

Doesn't LuaJ mess up characters over 127?

At least when sending over modems, yes. Also, according to various people, at Certain Other Unspecified Times. This is obviously a hindrance to UTF-8 or extended ASCII, but might be solvable (particularly as, according to chatter on the IRC channel, LuaJ may be going away at some point).

[Dave-ee Jones]

There goes paintutils...

[theoriginalbit]

AutoLocK, on 16 October 2013 - 02:27 AM, said:

There goes paintutils...

What are you on about now? Paintutils has nothing to do with fonts, ascii support or LuaJ!

[Cranium]

Correct, paintutils has nothing to do with fonts. It doesn't even use fonts.

I'd hate to have to lock this thread for ignorant posts.

[theoriginalbit]

oh also, even if paintutils did have something to do with fonts, ascii support, or LuaJ, dan and Cloudy would do everything in their power to make sure the API stayed around and worked in a way that it previously did so that programs made for previous versions would still work.

[jay5476]

AutoLocK, on 16 October 2013 - 02:27 AM, said:

There goes paintutils...

cloudy and dan would never remove something like that ( in my opinion ) it is working great atm and they wouldn't just go
stiff shit we don't like colors no more, no logos etc.
paint utils is a major addition and also one of the few features ( but awesome ) that computercraft has
Edit: they try and help us by not making old code incompatible with new updates what about firewolf,LyqydOS and other program's that use paint utils
this is why they are not changing to lua 5.2
(personally i never used lua 5.2 and dont see how it could be any greater )

[Engineer]

jay5476, on 23 October 2013 - 05:08 AM, said:

cloudy and dan would never remove something like that ( in my opinion ) it is working great atm and they wouldn't just go
stiff shit we don't like colors no more, no logos etc.
paint utils is a major addition and also one of the few features ( but awesome ) that computercraft has
Edit: they try and help us by not making old code incompatible with new updates what about firewolf,LyqydOS and other program's that use paint utils
this is why they are not changing to lua 5.2
(personally i never used lua 5.2 and dont see how it could be any greater )

Thanks for repeating something that has already been said! Seriously, come on. You definitely should have seen that theoriginalbit posted before the exact same with what you are trying to say:

theoriginalbit, on 16 October 2013 - 10:58 AM, said:

oh also, even if paintutils did have something to do with fonts, ascii support, or LuaJ, dan and Cloudy would do everything in their power to make sure the API stayed around and worked in a way that it previously did so that programs made for previous versions would still work.

Paintutils cannot be gone, just because its background. It has nothing to do with fonts! Also stated by theoriginalbit though:

theoriginalbit, on 16 October 2013 - 02:33 AM, said:

What are you on about now? Paintutils has nothing to do with fonts, ascii support or LuaJ!

So where are we actually afraid of? We could only benifite from it, from my view of point.

[Lyqyd]

jay5476, on 23 October 2013 - 05:08 AM, said:

Edit: they try and help us by not making old code incompatible with new updates what about firewolf,LyqydOS and other program's that use paint utils

LyqydOS does not include any calls to the paintutils API.

If any further discussion does not get back on track, this topic will be locked. Try speculating on how the changes to signs allowing more characters might play out or something.

[TheOddByte]

I just want to ask( To the moderator who replies, Probably Lyqyd ): Is this something you actually would consider adding into ComputerCraft?
Since this would be great for making oldschool games for computercraft or just games overall for it.
I do believe that all the CC users would just be happy if this would be added to CC since it doesn't mess with the mod that much and it is a reasonable suggestion IMO. This could make a lot of cool looking programs( Even though they are very cool already )

[Lyqyd]

Mojang is making changes to make more characters available to use in signs. Wait patiently and see if Dan chooses to extend the character set for CC as well. I wouldn't particularly expect it to happen though.

[Cranium]

I do remember him saying in IRC aaages ago before I was moderator that he does want to be able to allow other characters, for some other non-romanized languages, but that at the time, it was either too much trouble, or not possible.