aboutsummaryrefslogtreecommitdiff
path: root/content/matchlang.article
diff options
context:
space:
mode:
authorMarcel van Lohuizen <mpvl@golang.org>2016-02-10 21:35:49 +0100
committerMarcel van Lohuizen <mpvl@golang.org>2016-02-10 20:37:58 +0000
commit42ece10ea54a416684fd9f5e06d65c7dbaa5c125 (patch)
treea34101742cd2935b9d79ce8ec10120099b541e45 /content/matchlang.article
parent0b4f2c6358e7daac4cef4c37461aef6296b7b390 (diff)
content/matchlang: disable .play
text repo is not in yet. Change-Id: I76dcd2e86e9c2d1f98f08f233533b996a0cedf91 Reviewed-on: https://go-review.googlesource.com/19418 Reviewed-by: Marcel van Lohuizen <mpvl@golang.org>
Diffstat (limited to 'content/matchlang.article')
1 files changed, 4 insertions, 3 deletions
diff --git a/content/matchlang.article b/content/matchlang.article
index 8548590..ab8a7d0 100644
--- a/content/matchlang.article
+++ b/content/matchlang.article
@@ -10,7 +10,8 @@ Consider an application, such as a web site, with support for multiple languages
in its user interface.
When a user arrives with a list of preferred languages, the application must
decide which language it should use in its presentation to the user.
-This requires finding the best match between the languages the applications supports and those the user prefers.
+This requires finding the best match between the languages the applications supports
+and those the user prefers.
This post explains why this is a difficult decision and how how Go can help.
* Language Tags
@@ -135,7 +136,7 @@ based on data published in the Unicode Common Locale Data Repository (CLDR).
Here is a sample program, explained below, matching a user's language
preferences against an application's supported languages:
-.play -edit matchlang/complete.go
+.code -edit matchlang/complete.go
** Creating Language Tags
@@ -271,7 +272,7 @@ It also contains a “Self” namer for displaying a tag in its own language.
For example:
-.play -edit matchlang/display.go /START/,/END/
+.code -edit matchlang/display.go /START/,/END/
prints