ok, I will try it later.
在 2019年5月5日星期日 UTC+8下午9:18:48，claudep写道：
>
> Unfortunately, I cannot explain why this is not working, as the same
> string seemed to translate fine for other languages like French or Korean.
>
> When you build the translation locally, you might try to parse the
> sphinx
Unfortunately, I cannot explain why this is not working, as the same
string seemed to translate fine for other languages like French or Korean.
When you build the translation locally, you might try to parse the
sphinx building logs, looking for some warning related to that string.
Claude
Le 05.0
Actually, this problem exists longer than a year.
在 2019年5月4日星期六 UTC+8下午4:54:36，claudep写道：
>
> I suspect the problem is due to an initial space in the translations:
>
> " :class:`~django.db.models.ForeignKey` 类需要添加一个位置参数，即你想要
> 关联的"
> " :class:`~django.db.models.ManyToManyField` 类需要添加一个位置参数，即
I suspect the problem is due to an initial space in the translations:
" :class:`~django.db.models.ForeignKey` 类需要添加一个位置参数，即你想要
关联的"
" :class:`~django.db.models.ManyToManyField` 类需要添加一个位置参数，即
你想要"
I cannot explain why this is a problem, but try to remove it and we'll
check in the next merge if thi
about question 1:
Is that you mean I need point out some paragraphs that has this problem or
what?
more detail about the example given above:
this paragraph has already translated but still show in english. This
paragraph was numbered as 1472 in topics. There are three paragraphs
contains the
Le 03.05.19 à 14:44, Stone Chen a écrit :
> Hi,
> I'm a translator from China, I have translated two parts(intro and
> index) of the django document.
> But I got some questions when I translating.
> 1.Since I have fully translated one page, sometimes I found few
> paragraphs were still in eng
