search for: win_iconv

...by >> "simplified" substitutes uncontrollably (depending on OS locale). The >> same goes with simply entering the code statements in R Console. >> >> The problem does not occur on OS with UTF-8 locale (Mac OS, Linux...) > I think this is a "feature" of win_iconv that is bundled with base R > on Windows (./src/extra/win_iconv). The character from your example is > not part of the latin1 (iso-8859-1) set, however, win-iconv seems to > do so anyway: > >> x <- "\U00159" >> print(x) > [1] "?" >> iconv(x, &...

...mplified" substitutes uncontrollably (depending on OS locale). The > >> same goes with simply entering the code statements in R Console. > >> > >> The problem does not occur on OS with UTF-8 locale (Mac OS, Linux...) > > I think this is a "feature" of win_iconv that is bundled with base R > > on Windows (./src/extra/win_iconv). The character from your example is > > not part of the latin1 (iso-8859-1) set, however, win-iconv seems to > > do so anyway: > > > >> x <- "\U00159" > >> print(x) > > [1...

Hello, There is a long-lasting problem with processing UTF-8 source code in R on Windows OS. As Windows do not have "UTF-8" locale and R passes source code through OS before executing it, some characters are "simplified" by the OS before processing, leading to undesirable changes. Minimalistic example: Let's type "?" (LATIN SMALL LETTER R WITH CARON) in RGui

...acters are replaced by > "simplified" substitutes uncontrollably (depending on OS locale). The > same goes with simply entering the code statements in R Console. > > The problem does not occur on OS with UTF-8 locale (Mac OS, Linux...) I think this is a "feature" of win_iconv that is bundled with base R on Windows (./src/extra/win_iconv). The character from your example is not part of the latin1 (iso-8859-1) set, however, win-iconv seems to do so anyway: > x <- "\U00159" > print(x) [1] "?" > iconv(x, 'UTF-8', 'iso-8859-1'...

...t; substitutes uncontrollably (depending on OS locale). The >>>> same goes with simply entering the code statements in R Console. >>>> >>>> The problem does not occur on OS with UTF-8 locale (Mac OS, Linux...) >>> I think this is a "feature" of win_iconv that is bundled with base R >>> on Windows (./src/extra/win_iconv). The character from your example is >>> not part of the latin1 (iso-8859-1) set, however, win-iconv seems to >>> do so anyway: >>> >>>> x <- "\U00159" >>>> pri...

...;>>>>>> same goes with simply entering the code statements in R Console. > >>>>>>> > >>>>>>> The problem does not occur on OS with UTF-8 locale (Mac OS, Linux...) > >>>>>> I think this is a "feature" of win_iconv that is bundled with base R > >>>>>> on Windows (./src/extra/win_iconv). The character from your example is > >>>>>> not part of the latin1 (iso-8859-1) set, however, win-iconv seems to > >>>>>> do so anyway: > >>>>>&g...

Hello. When trying to compile R-3.0.2 on Windows 7 64bit, I get an error relating to "alone_decoder.c: Permission denied." The entire error code is copied below. gcc -std=gnu99 -m64 -shared -o Riconv.dll Riconv.def win_iconv.o touch stamp gcc -std=gnu99 -m64 -I../../include -I. -Iapi -DLZMA_API_STATIC -DHAVE_CONFIG_H -DWIN32 -O3 -Wall -pedantic -march=core-avx-i -O3 --param l1-cache-line-size=64 --param l1-cache-size=32 --param l2-cache-size=256 -c alone_decoder.c -o alone_decoder.o cc1.exe: fatal error: alone...

...bzlib xz PCRE #> "1.2.11" "1.0.8, 13-Jul-2019" "5.2.4" "10.33 2019-04-16" #> ICU TRE iconv readline BLAS #> "58.2" "TRE 0.8.0 R_fixes (BSD)" "win_iconv" "" "" ``` Let me know if there's any more information I can provide to help replicate and isolate the issue. Also, if this happens to be the expected behavior, I'd be keen to learn about why that's the case. Thank you, -Carson -- Carson...

...xtSoftVersion() zlib bzlib xz "1.2.8" "1.0.6, 6-Sept-2010" "5.0.8" PCRE ICU TRE "8.36 2014-09-26" "53.1" "TRE 0.8.0 R_fixes (BSD)" iconv "win_iconv" Hope it helps, ~p On Thu, Jan 28, 2016 at 6:32 AM, Dirk Eddelbuettel <edd at debian.org> wrote: > > On 28 January 2016 at 09:00, Dario Strbenac wrote: > | The capabilities function gives a logical result of which features R has > been compiled with. Is there a more advanc...

...cluded non-representable characters. That would increase the code complexity, increase performance overhead, but wake up existing bugs with smaller probability.? Note - some code that relied previously on best-fit conversions done by Windows will have been broken anyway. We would have to bypass win_iconv/iconv for that (adding more complexity). Bugs in code not handling encodings properly would still be triggered via non-representable characters. I've recently changed file.path() in R-devel to be slightly more conservative again, along these lines. We can still do it more widely, but it is...

...bzlib xz > "1.2.8" "1.0.6, 6-Sept-2010" "5.0.8" > PCRE ICU TRE > "8.36 2014-09-26" "53.1" "TRE 0.8.0 R_fixes (BSD)" > iconv > "win_iconv" > Hope it helps, > ~p Sure does, thank you. What also helps is reading RFM : The thread started with 'capabilities' and ?capabilities has a prominent link to extSoftVersion and that itself mentions grSoftVersion ... (and few more such functions!). Martin...

I recently built R-devel on Windows XP (sessionInfo below), and when loading libraries that require the iconv.dll was getting an error stating that 'This application has failed to start because iconv.dll was not found. Re-installing the application may fix this problem.'. An R-2.8.1 that I installed using the Windows installer has this dll in R-2.8.1/bin, whereas in R-devel it is still in

Please note that building R on Windows is documented in "R Installation and Administration", including links to external software. Particularly there is a link to texinfo which is part of Rtools. The documentation is maintained and it is a sufficient source of information for building R on Windows. https://cran.r-project.org/doc/manuals/r-release/R-admin.html

Hi Tomas, Sorry for the false alarm! I did some further testing, and you were right. There was no regression. I suspected it was a regression because the user who reported the issue said his code worked in R 3.6 but not 4.0. I should have tested it more carefully by myself. After I tested it again with the German locale and Chinese locale, respectively, I found that the code worked for both