On 2022-10-18 21:53, peter dalgaard wrote:
On 18 Oct 2022, at 16:37 , Dirk Eddelbuettel
wrote:
On 17 October 2022 at 13:20, Göran Broström wrote:
| G;ran (US keyboard)
:)
A fortunes candidate?
Incidentally, he's Gæran on a DK keyboard but Gøran on an NO one. The
three Scandinavian
> On 18 Oct 2022, at 16:37 , Dirk Eddelbuettel wrote:
>
>
> On 17 October 2022 at 13:20, Göran Broström wrote:
>
> | G;ran (US keyboard)
>
> :)
>
> A fortunes candidate?
>
Incidentally, he's Gæran on a DK keyboard but Gøran on an NO one. The three
Scandinavian languages have the same th
On 17 October 2022 at 13:20, Göran Broström wrote:
| Thanks Ivan,
|
| I found two simple ways to convert this old file to UTF-8:
|
| (i) In emacs, C-x f (default is utf-8)
That's a good ti[. I had actually hand-edited two lines down to 'seven bits'
instead of this. Umlaute, accents and spec
Thanks Ivan,
I found two simple ways to convert this old file to UTF-8:
(i) In emacs, C-x f (default is utf-8)
(ii) In RStudio, set Tools-Global Options-Code-Saving-
Default text encoding to UTF-8
No problem with new files.
G;ran (US keyboard)
Den 2022-10-17 kl. 11:18, skrev Ivan Krylov:
В Mon, 17 Oct 2022 11:07:25 +0200
Göran Broström пишет:
> warning: invalid UTF-8 in comment [-Winvalid-utf8]
> (It's my name)
>
> So I wonder: How do I make valid UTF-8 in comment?
The file GB_zeroin.c is saved in Latin-1 encoding. The warning should
go away once you convert it to UTF-8.
--
B
Hello,
I suddenly get Warnings from CRAN (clang):
warning: invalid UTF-8 in comment [-Winvalid-utf8]
(It's my name)
So I wonder: How do I make valid UTF-8 in comment?
(I already have "Encoding: UTF-8" in the DESCRIPTION file)
Thanks, Göran
__
R-pac
