Open GoogleCodeExporter opened 9 years ago
[deleted comment]
Original comment by zero...@zeromus.org
on 10 Jun 2014 at 10:55
Works fine for me in previous versions, and in the current version. Of course,
I don't know what encoding to use, so I just get nonsense. Please supply a lua
script which prints japanese for us to test with.
Original comment by zero...@zeromus.org
on 10 Jun 2014 at 11:54
Original comment by zero...@zeromus.org
on 10 Jun 2014 at 11:55
"It is not displayed"
Does this mean that you get a blank screen, or that you get garbage?
Original comment by zero...@zeromus.org
on 11 Jun 2014 at 1:21
gui.text(0,120,"てすとテスト手巣戸TESTtest")
Original comment by mario...@gmail.com
on 11 Jun 2014 at 12:25
Attachments:
So, "It is not displayed" means that you get a blank screen.
Is this the script which printed japanese in old versions of bizhawk? It's just
one line of code. In fact, I need the whole script, as an attachment, so that
whatever text encoding that file is using makes it through.
We've researched the issue further and actually disbelieve that japanese text
ever printed in bizhawk, so before we can proceed, we need proof.
Original comment by zero...@zeromus.org
on 11 Jun 2014 at 6:05
Bizhawk 1.6.1 work.
The sentence currently used for Lua is only this.
while true do
gui.text(0,120,"てすとテスト手巣戸TESTtest")
emu.frameadvance()
end
Original comment by mario...@gmail.com
on 12 Jun 2014 at 10:33
Attachments:
[deleted comment]
I've tried to reproduce your success with 1.6.1, and have not succeeded. I've
tried both GDI and D3D renderers, and various encodings for the .lua file, all
resulting in the file failing to load or producing gibberish. In addition,
looking at the LuaInterface source code, there's every evidence that it mashes
up character encodings soundly.
I believe you, but I think it worked for you in 1.6.1 due to some happenstance
in matching encodings in various things, possibly aided by locale setting and
other such stuff.
Moving forward, I want our Lua system to support unicode text, but I don't
think it ever really did before and so I'm entering this as a feature request
and not a bugfix.
Original comment by goyu...@gmail.com
on 13 Jun 2014 at 4:33
[deleted comment]
[deleted comment]
We need *THE WHOLE SCRIPT, AS AN ATTACHMENT, SO THAT WHATEVER TEXT FILE
ENCODING THAT FILE IS USING MAKES IT THROUGH*. Put it a in a Zip file.
Also, perhaps the OS language (the current locale) is involved in how some of
the text processing gets done at one stage or another.
Original comment by zero...@zeromus.org
on 13 Jun 2014 at 5:43
Bizhawk 1.7.3 and 1.7.4 not work.
lua is contained in the Zip file.
As for Japanese and some signs, no indication is given.
Original comment by mario...@gmail.com
on 7 Aug 2014 at 2:33
Attachments:
The file you provided doesnt work for me in bizhawk 1.6.1. Maybe as goyuken
says, your OS language or encoding is relevant. His analysis is still valid: if
this ever worked, it was an accident, and we need to undertake it seriously
when the time comes.
Original comment by zero...@zeromus.org
on 3 Sep 2014 at 1:12
Bizhawk 1.9.2 not work.
lua of the name decided by the character 2 bytes doesn't normally work.
Original comment by mario...@gmail.com
on 17 Jan 2015 at 2:54
Attachments:
Here's the above LUA script with Notepad's three Unicode formats. Unicode,
Unicode Big Endian, UTF-8
I get what the screenshot shows. ???? and Test. Not Japanese text.
Original comment by hegyak
on 10 Apr 2015 at 2:41
Attachments:
3 lua files were tried, but a Japanese text wasn't indicated.
Original comment by mario...@gmail.com
on 11 Apr 2015 at 12:00
Original issue reported on code.google.com by
mario...@gmail.com
on 10 Jun 2014 at 1:05