explosion/spaCy
1
1
Fork 0
mirror of https://github.com/explosion/spaCy.git synced 2024-12-25 17:36:30 +03:00
Code Issues Packages Projects Releases Wiki Activity

Fix formatting

Browse Source
This commit is contained in:
ines 2017-06-04 13:14:00 +02:00
parent 1d3b012e56
commit 7a66c9f039
2 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/docs/usage/_spacy-101/_language-data.jade
View File

@ -5,7 +5,7 @@ p
| #[strong exceptions and special cases], especially amongst the most
| common words. Some of these exceptions are shared across languages, while
| others are #[strong entirely specific] – usually so specific that they need
| to be hard-coded. The #[+src(gh("spaCy", "spacy/lang")) /lang] module
| to be hard-coded. The #[+src(gh("spaCy", "spacy/lang")) lang] module
| contains all language-specific data, organised in simple Python files.
| This makes the data easy to update and extend.

20
website/docs/usage/adding-languages.jade
View File

@ -7,6 +7,16 @@ p
| spaCy library. This guide explains how to fit everything together, and
| points you to the specific workflows for each component.
+aside("Working on spaCy's source")
| To add a new language to spaCy, you'll need to
| #[strong modify the library's code]. The easiest way to do this is to
| clone the #[+src(gh("spaCy")) repository] and #[strong build spaCy from source].
| For more information on this, see the #[+a("/docs/usage") installation guide].
| Unlike spaCy's core, which is mostly written in Cython, all language
| data is stored in regular Python files. This means that you won't have to
| rebuild anything in between – you can simply make edits and reload spaCy
| to test them.
+grid.o-no-block
+grid-col("half")
p
@ -39,16 +49,6 @@ p
+item #[+a("#vocabulary") Building the vocabulary]
+item #[+a("#training") Training]
+aside("Working on spaCy's source")
| To add a new language to spaCy, you'll need to
| #[strong modify the library's code]. The easiest way to do this is to
| clone the #[+src(gh("spaCy")) repository] and #[strong build spaCy from source].
| For more information on this, see the #[+a("/docs/usage") installation guide].
| Unlike spaCy's core, which is mostly written in Cython, all language
| data is stored in regular Python files. This means that you won't have to
| rebuild anything in between – you can simply make edits and reload spaCy
| to test them.
+h(2, "101") Language data 101
include _spacy-101/_language-data