Displaying 5 results from an estimated 5 matches for "iswprint".
Did you mean:
isprint
2017 May 09
1
source(), parse(), and foreign UTF-8 characters
...e than 500 hits on R-devel, and I suspect that checking each of
them will take some time, one way or another.
>
> You offered to spend time on this. I'd appreciate some checks of the
> patch I'm developing for 16098, and also some research into how
> certain things (e.g. the iswprint function) are handled on Windows.
I have looked in SVN, but couldn't find commits authored by you related
to this bug in any of the branches. Could you please point me at your
patch, or send it to me? Thanks!
-Kirill
>
> Duncan Murdoch
>>
>> I'm sure I've missed...
2007 Nov 23
3
[LLVMdev] Getting rid of the DoesntAccessMemoryFns and OnlyReadsMemoryFns tables
...ly
ispunct readnone readonly
isspace readnone readonly
isupper readnone readonly
tolower readnone readonly
toupper readnone readonly
iswalnum readnone readonly
iswalpha readnone readonly
iswcntrl readnone readonly
iswdigit readnone readonly
iswgraph readnone readonly
iswlower readnone readonly
iswprint readnone readonly
iswpunct readnone readonly
iswspace readnone readonly
iswupper readnone readonly
iswxdigit readnone readonly
towlower readnone readonly
towupper readnone readonly
iswctype readnone nothing
towctrans readnone nothing
btowc readnone nothing
wctob readnone nothing
nan readonly rea...
2017 May 09
2
source(), parse(), and foreign UTF-8 characters
Hi
I'm having trouble sourcing or parsing a UTF-8 file that contains
characters that are not representable in the current locale ("foreign
characters") on Windows. The source() function stops with an error, the
parse() function reencodes all foreign characters using the <U+xxxx>
notation. I have added a reproducible example below the message.
This seems well within the
2017 May 09
0
source(), parse(), and foreign UTF-8 characters
...ntil you actually need to write to a file. Other systems
tend to have UTF-8 locales in common use, so they're already fine.
You offered to spend time on this. I'd appreciate some checks of the
patch I'm developing for 16098, and also some research into how certain
things (e.g. the iswprint function) are handled on Windows.
Duncan Murdoch
>
> I'm sure I've missed many potential pitfalls, your input is greatly
> appreciated. Thanks for your attention.
>
> Further ressources: A write-up by Prof. Ripley [2], a section in R-ints
> [3], a blog post by Ista Zahn [...
2016 Jan 19
6
FWD: [patch] scp + UTF-8
Hi,
Martijn sent the following patch to me in private and agreed that i post
it here.
In any other program in OpenBSD base, i'd probably agree with the
basic approach. Regarding OpenSSH, however, i worry whether wcwidth(3)
can be used. While wcwidth(3) is POSIX, it is not ISO C. Does
OpenSSH target platforms that don't provide wcwidth(3)? If so,
do you think the problem can be solved