summaryrefslogtreecommitdiffstats
path: root/linguistics/src/main/java/com/yahoo/language/simple/SimpleDetector.java
diff options
context:
space:
mode:
authorgjoranv <gjoranv@gmail.com>2018-06-19 11:51:52 +0200
committerGitHub <noreply@github.com>2018-06-19 11:51:52 +0200
commit017d615e0aee5cb9210f2af9403819f51349f07a (patch)
tree66187ef99268d2a721ede2ef0f1c3db1522e222c /linguistics/src/main/java/com/yahoo/language/simple/SimpleDetector.java
parent475256fb2ce39ef87f352655b8d4c66a70791999 (diff)
parent3eae0d34a00570add245e39830452acded0c0238 (diff)
Merge pull request #6228 from vespa-engine/bratseth/nonfunctional-changes
Nonfunctional changes only
Diffstat (limited to 'linguistics/src/main/java/com/yahoo/language/simple/SimpleDetector.java')
-rw-r--r--linguistics/src/main/java/com/yahoo/language/simple/SimpleDetector.java4
1 files changed, 2 insertions, 2 deletions
diff --git a/linguistics/src/main/java/com/yahoo/language/simple/SimpleDetector.java b/linguistics/src/main/java/com/yahoo/language/simple/SimpleDetector.java
index 290d6744c2c..e6ce4eddb59 100644
--- a/linguistics/src/main/java/com/yahoo/language/simple/SimpleDetector.java
+++ b/linguistics/src/main/java/com/yahoo/language/simple/SimpleDetector.java
@@ -10,7 +10,7 @@ import com.yahoo.text.Utf8;
import java.nio.ByteBuffer;
/**
- * <p>Includes functionality for determining the langCode from a sample or from the encoding. Currently only Chinese,
+ * Includes functionality for determining the langCode from a sample or from the encoding. Currently only Chinese,
* Japanese and Korean are supported. There are two ways to guess a String's langCode, by encoding and by character
* set. If the encoding is available this is a very good indication of the langCode. If the encoding is not available,
* then the actual characters in the string can be used to make an educated guess at the String's langCode. Recall a
@@ -18,7 +18,7 @@ import java.nio.ByteBuffer;
* Unfortunately, its not 100% fool-proof. From what I've been able to determine, Korean characters do not overlap with
* Japanese or Chinese characters, so their presence is a good indication of Korean. If a string contains phonetic
* japanese, this is a good indication of Japanese. However, Japanese and Chinese characters occupy many of the same
- * character blocks, so if there are no definitive signs of Japanese then it is assumed that the String is Chinese.</p>
+ * character blocks, so if there are no definitive signs of Japanese then it is assumed that the String is Chinese.
*
* @author Rich Pito
*/