Displaying 6 results from an estimated 6 matches for "mbcs_get_next".
2018 Apr 28
2
[Bug report] Chinese characters are not handled correctly in Rterm for Windows
...wo ways. The WriteConsoleA variant uses the current console CP settings, and it should behave like fputc.
I guess the Rterm uses its own console I/O mechanism so the 2nd parameter of fputc is not stdout's handle. (I tried to read the source but unable to figure out how it works). The crash in mbcs_get_next, which is also mentioned in the previous post, may be related to this mechanism.
If you need further information, please let me know.
Thanks,
i at azurefx.name
Tomas Kalibera <tomas.kalibera at gmail.com> 2018/4/5 22:42
>
>
>Thank you for the report and initial debugging. I am n...
2006 May 16
1
Cannot load irr package
...text html latex example
** building package indices ...
* DONE (irr)
The downloaded packages are in
/tmp/RtmpsZJJ1h/downloaded_packages
But it won't load. Any ideas?
> library(irr)
Error in parse(n = -1, file = file) : invalid multibyte character in
mbcs_get_next
Error: unable to load R code in package 'irr'
Thanks.
Rick B.
2008 May 03
1
error with R-patched (2008-05-02 r45591)
...()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
Loading required package: utils
[1] "packages do not need updated"
Error in source(source.files[i]) :
invalid multibyte character in mbcs_get_next at line 17
[Previously saved workspace restored]
> sessionInfo()
R version 2.7.0 Patched (2008-05-02 r45591)
x86_64-unknown-linux-gnu
locale:
LC_CTYPE=en_US.UTF-8;LC_NUMERIC=C;LC_TIME=en_US.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=C;LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=C;LC_ADD...
2018 Mar 08
2
[Bug report] Chinese characters are not handled correctly in Rterm for Windows
...MERIC=C;LC_
TIME=Chinese (Simplified)_China.936"
4. > print("ABC\u4f60\u597dDEF")
[1] "ABCDEF"
(Unicode code points for "???")
5. Use Microsoft Pinyin IME to type "???" into the console. An error message appeared:
> invalid multibyte character in mbcs_get_next
Then the program crashed. My debugger reported a heap corruption, displayed as follows:
0x00007FFE2F3687BB (ntdll.dll) (Rterm.exe ??)??????????????: 0xC0000374: ??????? (????: 0x00007FFE2F3CC6E0)??
However, if the text is pasted into the console, it will not crash.
---ADDITIONAL INFO---
Both 32-bi...
2018 May 04
0
[Bug report] Chinese characters are not handled correctly in Rterm for Windows
Thanks for the update. I believe I've fixed a part of the problem you
have reported, the crash while entering Chinese characters to the
console (e.g. via Pinyin, the error message about invalid multibyte
character in mbcs_get_next). The fix is in R-devel 74693 - Windows
function ReadConsoleInputA no longer works with multibyte characters (it
is not documented, probably a Windows bug, according to reports online
this problem exists since Windows 8, but I only reproduced/tested in
Windows 10). Could you please verify the c...
2018 Apr 05
0
[Bug report] Chinese characters are not handled correctly in Rterm for Windows
...fied)_China.936"
>
> 4. > print("ABC\u4f60\u597dDEF")
> [1] "ABCDEF"
> (Unicode code points for "???")
>
> 5. Use Microsoft Pinyin IME to type "???" into the console. An error message appeared:
>> invalid multibyte character in mbcs_get_next
> Then the program crashed. My debugger reported a heap corruption, displayed as follows:
> 0x00007FFE2F3687BB (ntdll.dll) (Rterm.exe ??)???????????????: 0xC0000374: ??????? (????: 0x00007FFE2F3CC6E0)??
> However, if the text is pasted into the console, it will not crash.
>
> ---ADDI...