@@ -511,21 +511,6 @@ very large numerical matrices: see @code{scan} below.
511
511
Some of the issues to consider are:
512
512
513
513
@enumerate
514
- @item @strong {Encoding }
515
-
516
- If the file contains non-@acronym {ASCII } character fields, ensure that
517
- it is read in the correct encoding. This is mainly an issue for reading
518
- Latin-1 files in a UTF-8 locale, which can be done by something like
519
-
520
- @example
521
- read.table("file.dat", fileEncoding="latin1")
522
- @end example
523
-
524
- @noindent
525
- Note that this will work in any locale which can represent Latin-1
526
- strings, but not many Greek/Russian/Chinese/Japanese @dots {} locales.
527
-
528
-
529
514
@item @strong {Header line }
530
515
531
516
We recommend that you specify the @code {header } argument explicitly,
@@ -664,7 +649,19 @@ that Unicode escapes such as @code{\u@var{xxxx}} are never interpreted.
664
649
665
650
@item @strong {Encoding }
666
651
667
- This can be specified by the @code {fileEncoding } argument, for example
652
+ If the file contains non-@acronym {ASCII } character fields, ensure that
653
+ it is read in the correct encoding. This is mainly an issue for reading
654
+ legacy Latin-1 files in a UTF-8 locale, which can be done by something like
655
+
656
+ @example
657
+ read.table("file.dat", fileEncoding = "latin1")
658
+ @end example
659
+
660
+ @noindent
661
+ Note that this will work in any locale which can represent Latin-1
662
+ strings, but not many Greek/Russian/Chinese/Japanese @dots {} locales.
663
+
664
+ Other examples for the @code {fileEncoding } argument include:
668
665
669
666
@example
670
667
fileEncoding = "UCS-2LE" # Windows 'Unicode' files
@@ -928,7 +925,7 @@ X11 P 23646 50333 V2
928
925
...
929
926
@end example
930
927
931
- @findex unstack.
928
+ @findex unstack
932
929
Function @code {unstack } goes in the opposite direction, and may be
933
930
useful for exporting data.
934
931
0 commit comments