python / python-docs-ja Goto Github PK

View Code? Open in Web Editor NEW

63.0 17.0 32.0 180.14 MB

License: Other

Shell 100.00%

python document japanese

python-docs-ja's Introduction

Repository to store PO Files

https://www.python.org/dev/peps/pep-0545/#repository-for-po-files

Please see CONTRIBUTING.md

python-docs-ja's People

Contributors

Stargazers

Watchers

python-docs-ja's Issues

label of deprecated-removed directive is not translatable

A label of deprecated-removed directive is translatable when I submitted this PR, but become not translatable now.
Also, impl-detail directive is.

URL typo

python-docs-ja/tutorial/index.poの44行目にtypoがあります。
"Python Web サイト(htts://www.python.org) は、 Python "

以下のような修正が必要です。
"Python Web サイト(https://www.python.org) は、 Python "

branch 3.12 and 3.13

"python-newest" Transifex project is now alligned with 3.13, and python-312 is allogned with 3.12. This repository is uses default branch 3.11 pulling from python-newest.

Consider branching 3.12 and 3.13, and making 3.13 default.

PDF build issue

Since #34 and #31 I have issues building PDFs on docs.python.org, it can easily be reproduced using https://github.com/python/docsbuild-scripts/ as:

./build_docs.py --build-root ./build_root --www-root ./www --log-directory ./logs --group $(id -g) --skip-cache-invalidation --language ja --branch 3.9

(you can easily try other branches by changing the --branch argument)

Warnings during documentation build

While building the translation for 3.6, I got some inconsistent term references in translated message and some Inline interpreted text or phrase reference start-string without end-string..

Typically in https://github.com/python/python-docs-ja/blob/3.6/c-api/arg.po#L633:

msgid "Convert a Python integer to a C :c:type:`long long`."
msgstr "PythonのintをC :c:type:`long long`へ変換する。"

It looks like the rst parser does not like the へ to be glued to the backtick. I hoever don't know Japanese and can't tell if a space is acceptable or not here.

Some "inconsistend term references" looks to be legitimate (using a term reference when the term is used in the english version without reference) but some may not be, like: "https://github.com/python/python-docs-ja/blob/3.6/c-api/init.po#L1153 the translation speak about PyEval_RestoreThread but the english paragraph does not. Can't tell if it's an issue or deliberate though.

Here is a short extraction from the docs.python.org logs, tell me if you want more:

/srv/docsbuild/python36/Doc/library/doctest.rst:1386: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/doctest.rst:1409: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/doctest.rst:1546: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/doctest.rst:1556: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/doctest.rst:1698: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/doctest.rst:1794: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/email.header.rst:110: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/email.util.rst:116: WARNING: inconsistent footnote references in translated message
/srv/docsbuild/python36/Doc/library/exceptions.rst:460: WARNING: Inline interpreted text or phrase reference start-string without end-string.
/srv/docsbuild/python36/Doc/library/exceptions.rst:460: WARNING: Inline interpreted text or phrase reference start-string without end-string.
/srv/docsbuild/python36/Doc/library/exceptions.rst:460: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/exceptions.rst:465: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/functions.rst:1172: WARNING: Inline emphasis start-string without end-string.
/srv/docsbuild/python36/Doc/library/functions.rst:936: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/functions.rst:1143: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/functions.rst:1172: WARNING: Inline emphasis start-string without end-string.
/srv/docsbuild/python36/Doc/library/functions.rst:1533: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/gettext.rst:151: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/gettext.rst:316: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/gettext.rst:517: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/grp.rst:46: WARNING: inconsistent term references in translated message
/srv/docsbuild/python36/Doc/library/gzip.rst:64: WARNING: inconsistent term references in translated message

Enable scheduling of CI workflow update

I see that the schedule is disabled in the .github/workflows/update.yml workflow, and I would like to suggestion to have it enabled again.

Having a schedule set for running the update translations workflow is important for a couple reason. First one is that any contributions made for this language in Transifex that don't reach this repository won't be available in the generated translated documentation, because (as you may know) the Python infrastructure fetches translations from the language repository, not from Transifex.

Second reason is that this repository runs the command that updates the source strings in Transifex, tx push --source. Whenever there is a fix/change in the source documentation, the source strings in Transifex must be updated too; otherwise one might translate to 100%, but the generated translated documentation will still have some English sentences.

python 3.11 released

Now that Python 3.11 beta is available, how about updating Transifex project with this version?

Typo in collections.deque

See https://bugs.python.org/issue36830

test

Probable typo make PDF build fail

I got:

! Text line contains an invalid character.
l.66796 ...de{subprocess.Popen()}}}} の stream ^^P
                                                  引数など、ファイル記述子つ...

while building with xelatex, and found where it come from, it's from library/socket.po:

#: ../../library/socket.rst:1072
msgid ""
"On Windows, the file-like object created by :meth:`makefile` cannot be used "
"where a file object with a file descriptor is expected, such as the stream "
"arguments of :meth:`subprocess.Popen`."
msgstr ""
"Windows では、 :meth:`subprocess.Popen` の stream ^P引数など、ファイル記述子つき file "
"オブジェクトが期待されている場所では、 :meth:`makefile` によって作成される file-like オブジェクトは使用できません。"

Problem is the ^P right after the word stream. This ^P is the representation emacs makes of the charachter, which is a 0x10, so a data link escape.

git grep $'\x10' 
library/socket.po:"Windows では、 :meth:`subprocess.Popen` の stream ^P引数など、ファイル記述子つき file "

add Japansese Translation in What's New In Python 3.7

Hi.

I found some texts have not been translated into Japanese, even if they contain important information.
So I decided to make a pull request. Check it out if you have time.

Thanks.

:green_heart: Let's move from Travis to GitHubAction.

Hi all. How about moving CI from Travis to GitHubActions? Let me know what you think.

errnoのエラー・メッセージの相違に付いて

Got this on docs@, won't publish it there, but coping/pasting here becaues it may be of interest:

errnoのエラー・メッセージの相違に付いて
超初心者の私が初めて投稿するので、ここで良いのかも分かりません。
違っていましたら、お手数をお掛けしますが、消去しただければ、幸いです。

システムのエラー・メッセージとインストールされた「python
Documentation」、「errno.h」と「errno(3)」のエラー・メッセージに相違が見られます。
詳細は、添付ファイルを解凍して確認してください。「errnoの設定値確認.tar.xz」

展開後は「errno-python.txt」と「errnoの設定値確認.pdf」です。（ハイブリッドpdf）
pdfの使用文字は「TakaoPGothic」と「TakaoPMincho」ですので、インストールしていれば良いのですが！。
ubuntu 18.04 LTSには初期インストールがされていませんでした。

確認対象ファイル
システムのエラー・メッセージ
python Documentation Python 2.7.17
英語版 : Python » English 2.7.17 Documentation » The Python Standard
Library »
15. Generic Operating System Services » 15.16. errno —
Standard errno system symbols
https://docs.python.org/2.7/library/errno.html?highlight=errno#module-errno
日本語版 : Python » Japanese 2.7.17 ドキュメント » Python 標準ライブラリ
»
15. 汎用オペレーティングシステムサービス » 15.16. errno ---
標準の errno システムシンボル
https://docs.python.org/ja/2.7/library/errno.html?highlight=errno#module-errno
errno.h /usr/include/asm-generic/errno-base.hと
/usr/include/asm-generic/errno.h
errno(3) 4.15

いろんな環境でLinuxが使用されているようなので、「errno(3)」が違っているのは仕方ないとして、
インストールされた「python
Documentation」、「errno.h」とプログラムエラー時に出力されるエラー・メッセージが異なっているのはどうかと思います。「Python
3.8.2rc2」でも同様です。
一応、「errno.h」の方は、コメントどして説明されているようです。ネットでも確認はしたのですが、エラーに付いては、いろいろな問題があるようです。せめてインストールされたファイルでは相違が無いようにと心から願っています。
確認のほどよろしくお願いします。

私の環境
Description: Ubuntu 18.04.4 LTS 2020.02.25.作成
Linux 4.15.0-88-generic x86_64 GNU/Linux
gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
GNU C Library (Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27.
Python 2.7.17 です。

[email protected]
kiyokazu shikanai

secrets.tar is committed into repo

All secrets should be revoked immediately!

Improper discretionary list

Since 2019-12-25, around the time we bumped to Sphinx 2.3.1, I see this error in the logs:

[5]
第 3 章
[6] (/usr/share/texlive/texmf-dist/tex/latex/psnfss/omspcr.fd)
! Improper discretionary list.
\textbackslash ...tionary {\sphinx@textbackslash }
                                                  {\sphinxafterbreak }{\sphi...
l.196 ...nxcode{\sphinxupquote{\textbackslash{}0}}
                                                   が埋め込まれていても大丈...
? 
! Emergency stop.
\textbackslash ...tionary {\sphinx@textbackslash }
                                                  {\sphinxafterbreak }{\sphi...
l.196 ...nxcode{\sphinxupquote{\textbackslash{}0}}
                                                   が埋め込まれていても大丈...
Output written on howto-sockets.dvi (6 pages, 23844 bytes).
Transcript written on howto-sockets.log.
Latexmk: Index file 'howto-sockets.idx' was written
Latexmk: References changed.
Collected error summary (may duplicate other messages):
  latex: Command for 'latex' gave return code 256
Latexmk: Use the -f option to force complete processing,
 unless error was exceeding maximum runs of latex/pdflatex.
Latexmk: Errors, so I did not complete making targets
Makefile:35: recipe for target 'howto-sockets.pdf' failed

[6] (/usr/share/texlive/texmf-dist/tex/latex/psnfss/omspcr.fd)
! Improper discretionary list.
\textbackslash ...tionary {\sphinx@textbackslash }
                                                  {\sphinxafterbreak }{\sphi...
l.204 ...nxcode{\sphinxupquote{\textbackslash{}0}}
                                                   が埋め込まれていても大丈...

does it speak to someone?

Unicode character 顛 (U+C4CF) not set up for use with LaTeX.

Hi!

Here's a new error I discovered now that #22 is closed:

! Package inputenc Error: Unicode character 顛 (U+C4CF)
(inputenc)                not set up for use with LaTeX.

See the inputenc package documentation for explanation.
Type  H <return>  for immediate help.
 ...                                              
                                                  
l.762 ...er dotless i), \textquotesingle{}^^c5^^bf
                                                  \textquotesingle{} (U+017F...

Can someone take a look at it?

It can be reproduced by using:

python -m pip install git+https://github.com/sphinx-doc/sphinx/@4.0.x
make  'SPHINXOPTS=-D latex_engine=platex -D latex_elements.inputenc= -D latex_elements.fontenc= -j4 -q -D locale_dirs=/home/mdk/clones/python/docsbuild-scripts/build_root/3.11/locale -D language=ja -D gettext_compact=0' SPHINXERRORHANDLING= autobuild-dev

(replace the locale_dirs path to point to a directory containing ja/LC_MESSAGES containing a clone of this repo).

Found a bell character

On branch 2.7 only:

$ git grep $'\x07' 
installing/index.po:msgstr "Python プロジェクトの多くはソースに基いた配布に強く依存しており、インストールプロセスの一環として、^Gエンドユーザ環境でソースから拡張モジュールをコンパイルすることを期待します。"

It's right before エ, grep prints it as ^G for readability.

python / python-docs-ja Goto Github PK

python-docs-ja's Introduction

python-docs-ja's People

Contributors

Stargazers

Watchers

Forkers

python-docs-ja's Issues

Recommend Projects

Recommend Topics

Recommend Org