-
Notifications
You must be signed in to change notification settings - Fork 13
foundations/contentの翻訳 #290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -24,49 +24,46 @@ use crate::layout::{AlignElem, Alignment, Axes, Length, MoveElem, PadElem, Rel, | |||||
use crate::model::{Destination, EmphElem, LinkElem, StrongElem}; | ||||||
use crate::text::UnderlineElem; | ||||||
|
||||||
/// A piece of document content. | ||||||
/// ドキュメントのコンテンツ要素 | ||||||
/// | ||||||
/// This type is at the heart of Typst. All markup you write and most | ||||||
/// [functions]($function) you call produce content values. You can create a | ||||||
/// content value by enclosing markup in square brackets. This is also how you | ||||||
/// pass content to functions. | ||||||
/// この型は、Typstの中心となるものです。Typstのすべてのマークアップやほとんどの | ||||||
/// [関数]($function)はコンテンツを生成します。コンテンツ値は角括弧でマークアップを | ||||||
/// 囲むことで作成できます。これは、コンテンツを関数に渡す際にも使われる方法です。 | ||||||
/// | ||||||
/// # Example | ||||||
/// # 例 | ||||||
/// ```example | ||||||
/// Type of *Hello!* is | ||||||
/// #type([*Hello!*]) | ||||||
/// ``` | ||||||
/// | ||||||
/// Content can be added with the `+` operator, | ||||||
/// [joined together]($scripting/#blocks) and multiplied with integers. Wherever | ||||||
/// content is expected, you can also pass a [string]($str) or `{none}`. | ||||||
/// コンテンツは`+`演算子で追加したり、[結合]($scripting/#blocks)したり、整数と | ||||||
/// 乗算したりすることができます。コンテンツが期待される場所であれば、[文字列]($str)や | ||||||
/// `{none}`を渡すことも可能です。 | ||||||
/// | ||||||
/// # 表現 | ||||||
/// コンテンツはフィールドを持つ要素で構成されます。_要素関数_で要素を構築する際は、 | ||||||
/// フィールドを引数として提供します。コンテンツ値がある場合は、 | ||||||
/// [フィールドアクセス用シンタックス]($scripting/#field-access)でそのフィールドに | ||||||
ultimatile marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||
/// アクセスできます。 | ||||||
/// | ||||||
/// # Representation | ||||||
/// Content consists of elements with fields. When constructing an element with | ||||||
/// its _element function,_ you provide these fields as arguments and when you | ||||||
/// have a content value, you can access its fields with [field access | ||||||
/// syntax]($scripting/#field-access). | ||||||
/// フィールドの中には必須のものがあります。それらは要素を構築する際に提供する必要があるため、 | ||||||
/// その型のコンテンツでは常にフィールドアクセスを通じて利用可能です。 | ||||||
/// 必須フィールドはドキュメント内でそのようにマークされています。 | ||||||
/// | ||||||
/// Some fields are required: These must be provided when constructing an | ||||||
/// element and as a consequence, they are always available through field access | ||||||
/// on content of that type. Required fields are marked as such in the | ||||||
/// documentation. | ||||||
/// ほとんどのフィールドはオプションで、必須フィールドと同様に、単一要素を設定する | ||||||
/// ために要素関数に渡すことができます。しかし、[setルール]($styling/#set-rules)で | ||||||
/// 設定して、スコープ内のすべての要素に適用することも可能です。 | ||||||
/// オプションのフィールドは、要素関数に明示的に渡された場合にのみフィールドアクセス構文 | ||||||
|
/// オプションのフィールドは、要素関数に明示的に渡された場合にのみフィールドアクセス構文 | |
/// オプションのフィールドは、要素関数に明示的に渡された場合にのみフィールドアクセス用シンタックス |
Copilot uses AI. Check for mistakes.
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] The word 'もっている' should be written in hiragana as 'もっている' or in kanji as '持っている' for better readability.
/// することも可能です。 | |
/// することも可能です。特定の種類の要素を持っているかを確認するために、グローバル関数と比較 |
Copilot uses AI. Check for mistakes.
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] For consistency, 'もつ' should be written as '持つ' in kanji or 'もつ' should be consistently used throughout the translation.
Copilot uses AI. Check for mistakes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] The Japanese translation should be more precise. Consider using 'ドキュメントコンテンツの要素' or 'ドキュメントコンテンツ片' to better reflect 'A piece of document content'.
Copilot uses AI. Check for mistakes.