Skip to content

Conversation

masa-ita
Copy link
Contributor

images.ipynb and tf-records.ipynb in site/ja/tutorials/load_data are translated in Japanese.

@review-notebook-app
Copy link

Check out this pull request on ReviewNB: https://app.reviewnb.com/tensorflow/docs/pull/427

Visit www.reviewnb.com to know how we simplify your Jupyter Notebook workflows.

@googlebot googlebot added the cla: yes CLA has been signed label Mar 27, 2019
@lamberta lamberta added the translation Community-provided translation for certain languages label Mar 27, 2019
@lamberta
Copy link
Member

Thank you, Masatoshi!

@ohtaman, @taquo, @sfujiwara If you get a chance, please take a look :)

For future work, I would suggest looking at the TF 2.0 Alpha docs: https://www.tensorflow.org/alpha
Theses are located in the r2/ directory, but use /alpha for the translations, similiar to how the Korean translations are set up.

They are still a work-in-progress, but it is the way forward when TF 2.0 stable is released. And there is overlap with the TF 1.x tutorials.

Thank you!

@ohtaman
Copy link
Contributor

ohtaman commented Mar 30, 2019

Thank you, Masatoshi.

@lamberta I can review these *.ipynb next week (4/1~).

@masa-ita
Copy link
Contributor Author

@lamberta

Thanks.
I'd like to focus on the r2 tree next.

@@ -0,0 +1,3254 @@
{
Copy link
Contributor

@ohtaman ohtaman Apr 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These links should be changed from '"en/" to "ja"

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Fixed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked that this is fixed.

@@ -0,0 +1,3254 @@
{
Copy link
Contributor

@ohtaman ohtaman Apr 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. This cell does not exists in original notebook.
  2. Should remove outputs. (This contains your local path)

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops! Removed.

@@ -0,0 +1,3254 @@
{
Copy link
Contributor

@ohtaman ohtaman Apr 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This cell is changed(?) in original (and r2) notebook.

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well. Adopt changes.

@@ -0,0 +1,3254 @@
{
Copy link
Contributor

@ohtaman ohtaman Apr 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

memo: this cell is changed in original and r2 notebook.

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto.

@@ -0,0 +1,3254 @@
{
Copy link
Contributor

@ohtaman ohtaman Apr 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"以下は" is better than "これが" since "これが" can mean "the above code"

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exactly!

@@ -0,0 +1,3254 @@
{
Copy link
Contributor

@ohtaman ohtaman Apr 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

all_image_labelsall_image_pathsの配列がある場合

Maybe: all_image_labelsall_image_pathsような配列がある場合


Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right.

@@ -0,0 +1,3254 @@
{
Copy link
Contributor

@ohtaman ohtaman Apr 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: I prefer "展開" to "解体"

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. It's better.

@@ -0,0 +1,3254 @@
{
Copy link
Contributor

@ohtaman ohtaman Apr 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Very weak suggestion: "同じサイズに設定しています。" is better than "同じサイズに設定します。" Because, to set buffer_size the same size as the dataset is good in this case but not in other cases with larger datasets.
  2. In last paragraph, "を" are repeated.
  3. Suggestion: "tf.data.Dataset.apply メソッドを、...と組み合わせることで対処することができます。"

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good suggestions. Thanks.

@@ -0,0 +1,3254 @@
{
Copy link
Contributor

@ohtaman ohtaman Apr 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Weak suggestion: I prefer "形状" or "形" to "シェイプ" .

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to "形状".

@@ -0,0 +1,3254 @@
{
Copy link
Contributor

@ohtaman ohtaman Apr 2, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"期待通りの" may be better than "予定される"

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. It's better.

Copy link
Contributor

ohtaman commented Apr 2, 2019

I reviewed images.ipynb.

  • I compared translations with "r2/" directory version.
  • Most of all original text is unchanged in r2/ version and it seems very easy to apply to r2/.

Copy link
Contributor Author

masa-ita commented Apr 3, 2019

Additionally, I changed the word "イメージ" to ”画像" and "ロード" to "読み込み".

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestions:

  • "キャッシュする" may be frequently used than "キャッシングする"
  • "ファイルで表されます" should be "ファイルで定義されます" because the translation of "define" is "定義"
  • Should use same word for the ranslation of "message type". "メッセージの型" and "メッセージタイプ" are appeared.
  • I prefer "メッセージ型"

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you. Adopted your suggestion.

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Weak suggestion:

  • You can use "パース" as a translation of "parse". It is used in general enough.

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Use "パース" for "parse".

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The second paragraph is a little bit confusing.


この他の一般的なデータ型のほとんどは、強制的にこれらのうちの1つにすること可能です。


How about: (use the word "変換する")

その他の一般的なデータ型の多くは、これらの型のいずれかに強制的に変換することができます。


or, maybe it is better to remove "その他の" (translation of "other") for ease of understanding.

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Good suggestion.

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer "メッセージはすべて" or "すべてのメッセージ" to "主要なメッセージ" since the translation of "All" is "すべて" in general.

Reply via ReviewNB

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. Changed.

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

各値は上記の関数を使って3種類の互換性のある型をからなる

Typo?: 型をからなる

Maybe: 型のうちの1つだけを含む


#2で作成したマップを特徴量メッセージに変換します。

"Features メッセージ" seems better than "特徴量メッセージ" because

Features message is defined in "https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/example/feature.proto#L85".

Reply via ReviewNB

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This paragraph seems to be changed. In original text,


a boolean feature, False or True with equal probability
an integer feature uniformly randomly chosen from [0, 5)
a string feature generated from a string table by using the integer feature as an index
a float feature from a standard normal distribution


Translation example:

  • False または Trueを表す論理値。出現確率は等しいものとします。
  • [0, 5)の範囲から一様にサンプリングした整数値。
  • 整数特徴量をインデックスとした文字列テーブルを使って生成した文字列特徴量
  • 標準正規分布からサンプリングした浮動小数点数。



Reply via ReviewNB

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

# 整数特徴量 -10000 から 10000 の間の乱数
feature1 = np.random.randint(0, 5, n_observations)

This comment does not match to the code.


# バイト特徴量
strings = np.array([b'cat', b'dog', b'chicken', b'horse', b'goat'])

"文字列特徴量" or "バイト文字列特徴量" may be better than "バイト特徴量" since the original text is "string feature".

Reply via ReviewNB

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

 Each single observation will be written as a Features message as per the above. 

Reply via ReviewNB

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The original document seems be changed:

  • The "## TFRecords Format Details" section was added before this section.

Reply via ReviewNB

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"tf.python_io" is changed to "tf.io" in r2 version.

Reply via ReviewNB

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This cell is changed in r2 version.

Reply via ReviewNB

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI: This section is modified in r2 version (and so I compared only with original text)

Reply via ReviewNB

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very weak suggestion:

The translation of "image string" , "画像文字列", may be a bit confusing.

May be "生画像のデータ列" or just "生画像データ" is better than it.


Reply via ReviewNB

@@ -0,0 +1,1687 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI: This cell is changed in r2 version.

Reply via ReviewNB

Copy link
Contributor

ohtaman commented Apr 13, 2019

@masa-ita I finished adding comments to tf-records.ipynb now. It seems that you updated "tf_records.ipynb" instead of "tf_recordes.ipynb" in response to my comments I gave before.

@lamberta lamberta force-pushed the site_ja_tutorials_load_data branch from 3f4e900 to 1f01b90 Compare April 22, 2019 17:34
Copy link
Member

@lamberta lamberta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@lamberta lamberta added the ready to pull Start merge process label Apr 22, 2019
@TensorFlow-Docs-Copybara TensorFlow-Docs-Copybara merged commit faea3f1 into tensorflow:master Apr 22, 2019
TensorFlow-Docs-Copybara pushed a commit that referenced this pull request Apr 22, 2019
@lamberta lamberta added the ja label Apr 30, 2019
nedaresa pushed a commit to nedaresa/tensorflow-convolutional-neural-networks-optimization-key that referenced this pull request Mar 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes CLA has been signed ja ready to pull Start merge process translation Community-provided translation for certain languages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants