authorgravatar for luehmann@ponton.dePhilipp Lühmann <luehmann@ponton.de> 2021-08-31 11:49:17+02:00
committergravatar for andrew@ziglang.orgAndrew Kelley <andrew@ziglang.org> 2021-08-31 14:05:44-04:00
log76b85cd66583871c951e157bedd084dd45f5eba1
tree442c3f8ea30bdbf5e8f09fa6f5fa62a0732a1199
parent435d8ae5367a23699e0b8d2b68b9928367252a54

fix typo

1 files changed, 1 insertions(+), 1 deletions(-)

doc/langref.html.in+1-1
...@@ -783,7 +783,7 @@ pub fn main() void {...@@ -783,7 +783,7 @@ pub fn main() void {
783 Because Zig source code is {#link|UTF-8 encoded|Source Encoding#}, any non-ASCII bytes appearing within a string literal783 Because Zig source code is {#link|UTF-8 encoded|Source Encoding#}, any non-ASCII bytes appearing within a string literal
784 in source code carry their UTF-8 meaning into the content of the string in the Zig program;784 in source code carry their UTF-8 meaning into the content of the string in the Zig program;
785 the bytes are not modified by the compiler.785 the bytes are not modified by the compiler.
786 However, it is possible to embbed non-UTF-8 bytes into a string literal using <code>\xNN</code> notation.786 However, it is possible to embed non-UTF-8 bytes into a string literal using <code>\xNN</code> notation.
787 </p>787 </p>
788 <p>788 <p>
789 Unicode code point literals have type {#syntax#}comptime_int{#endsyntax#}, the same as789 Unicode code point literals have type {#syntax#}comptime_int{#endsyntax#}, the same as