This page is dedicated to showcasing how pitch accent is displayed, and various ways to edit said display. # What Is Pitch Accent? Here is a (slightly modified) excerpt taken from the [AJT Japanese Github page](https://github.com/Ajatt-Tools/Japanese#pitch-accent-what-is-that) that explains the notation well: !!! quote For more information on the Japanese pitch accent, I would like to refer you to [this wikipedia article](http://en.wikipedia.org/wiki/Japanese_pitch_accent). In short, the following notations can be found: - **Overline**: Indicates "High" pitch (see "Binary pitch" in Wikipedia article). - **Overline downstep**: usually means stressing the mora/syllable before. - **Red circle mark**: Nasal pronunciation. For example, げ would be a nasal け, and would represented as け°. - **Blue color**: Devoiced mora (barely pronounced at all). For example, ヒ would be closer to h than hi.
Likewise, ク would be more like a k than ku. --- # Specifying Pitch Accent The displayed pitch accent is usually the first position found in `PAPositions`. However, you can override this automatically chosen position using the `PAOverride` field. ![type:video](assets/autopa/pa_override.mp4) The demo above covers the most basic usage of `PAOverride`, which should suffice for most people. The rest of the page covers the details on exactly how `PAOverride` works, and all the ways to customize how the pitch accent is displayed. --- # Colored Pitch Accent The reading, word and pitch overline can be automatically colored in Migaku style colors, according to the pitch accent. This automatic coloring behavior is **disabled by default**, and must be enabled in the {{ RTO_FILE }}: ```json "autoPitchAccent.coloredPitchAccent.enabled": true, // (1)! ``` 1. The `autoPitchAccent` module must be enabled to use colored pitch accent. For example: ```json "autoPitchAccent.enabled": true, ``` This is enabled by default, so you likely don't need to manually enable this module. ![type:video](assets/autopa/pa_override_color.mp4) ## Pitch Accent Groups | Anki Tag | 日本語 | Example | Reading | |: ------- :|: ---- :|: ------------------ :|: ---------- :| | heiban | 平板 | 自然 {.pa-heiban} | しぜん￣ | | atamadaka | 頭高 | 人生 {.pa-atamadaka} | じ＼んせい | | nakadaka | 中高 | 弱点 {.pa-nakadaka} | じゃくて＼ん | | odaka | 尾高 | 道具 {.pa-odaka} | どうぐ＼ | | kifuku | 起伏 | 驚く {.pa-kifuku} | おどろ＼く | ## Controlling What Gets Colored {{ feature_version("0.12.0.0") }} There are many {{ RTOs }} that change exactly what is colored. By default, everything except words found in tooltips (kanji hover and word indicators) are highlighted. ```json "autoPitchAccent.coloredPitchAccent.color.wordReadingPitchOverline": true, "autoPitchAccent.coloredPitchAccent.color.wordReadingKanji": true, "autoPitchAccent.coloredPitchAccent.color.testedContent": true, "autoPitchAccent.coloredPitchAccent.color.fullSentence": true, "autoPitchAccent.coloredPitchAccent.color.definitions": true, "tooltips.overrideOptions.autoPitchAccent": { // highlights bolded kanji "autoPitchAccent.coloredPitchAccent.color.wordReadingKanji": false, // highlights bolded sentence below word "autoPitchAccent.coloredPitchAccent.color.fullSentence": false, // (1)! }, ``` 1. If you want enable word coloring within the sentence, the word within the sentence must be able to be highlighted in the first place. To enable this, use the following runtime option: ```json "tooltips.highlightWordInSentence": true, ``` ## When Pitch Is Not Automatically Colored Pitch accent coloring requires a numeric position value somewhere within the card. This is usually found in one of these places: * `PAPositions` * `PAOverride` * `AJTWordPitch` (the numeric position is automatically calculated through the HTML) Usually, `PAPositions` is automatically filled. In the cases where pitch accent coloring does not work as expected, your two main options are: 1. Using `PAOverride` with [a number](autopa.md#specifying-pitch-accent) (recommended). 2. Force the pitch accent group with tags (see below). ## Kifuku Coloring {{ feature_version("0.12.0.0") }} A word is automatically colored as 起伏 if the `WordTags` field contains a verb tag, and its pitch accent group is not 平板. This `WordTags` field can only be filled out if you have a modern version of the [JMdict dictionary for Yomichan](https://github.com/Aquafina-water-bottle/jmdict-english-yomichan) For old cards that do not have this field filled, you will have to manually mark the word with `-1` (in `PAOverride`). ## Override Pitch Accent Group In some extremely rare cases, you must set manually set the pitch accent group, if the available options do not work. To do this, add the appropriate tag to the card. The exact tags that can be used are shown in the [summary table](autopa.md#pitch-accent-groups) above, under the `Anki Tag` and 日本語 sections. For example, the tag can be `heiban`, `平板`, etc. !!! note The tag *only* overrides the pitch accent color, and does not affect the pitch accent representation itself. This fact can be useful for certain exceptions, such as how 通る is [1] instead of [2]. If you want to use the 起伏 pattern on 通る, you will have to set the `PAOverride` value to `1`, and then add the `起伏` tag. TODO image of above (without tag, with tag) --- # How Pitch Accent is Selected Pitch accent is selected based on the following priority: 1. [PAOverrideText](autopa.md#1-paoverridetext) 1. [PAOverride](autopa.md#2-paoverride) 1. [PAPositions](autopa.md#3-papositions) 1. [AJTWordPitch](autopa.md#4-ajtwordpitch) The first field that is non-empty will be the field that is used to display the pitch accent. !!! note When the `auto-pitch-accent` module is disabled, the priority changes to the following: 1. `PAOverrideText` 1. `PAOverride` 1. `AJTWordPitch` Of course, as the module is disabled, `PAOverride` will not be parsed in any way. More info on this can be found in the [PAOverride field](#2-paoverride) section below. --- # (1) PAOverrideText {{ feature_version("0.11.0.0") }} If the `PAOverrideText` field is filled, then this field is displayed exactly as is, without any changes or parsing. This provides the most flexibility, but the least ease of usage.

PAOverrideText with: "Hello world!"

--- # (2) PAOverride The `PAOverride` allows for two primary formats: positions and text format. If the field contents cannot be parsed in either of these formats, then the field is displayed without any special formatting. This will act just like `PAOverrideText`. ## (2.1) PAOverride: Positions Format When the `PAOverride` field contains any number, that number will be considered as the downstep position, and be rendered as such. The number `-1` represents the 起伏 pattern, and can be used to set the downstep to be after the second last mora. **Examples** (on the 偽者 card): | PAOverride | Result | Notes | |-|-|-| | `0` | ニセモノ | | | `1` | ニꜜセモノ | | | `-1` | ニセモꜜノ | 起伏 | ### Multiple Numbers {{ feature_version("0.11.0.0") }} Multiple numbers can be used, as long as they are separated by commas. This is useful on certain words with devoiced mora, where the pitch accent can be multiple positions with little real distinction. Additionally, individual numbers can be bolded to grey out the other positions. This is useful to highlight the correct pitch accent among all possiblities. **Examples** (on the 偽者 card): | PAOverride | Result | Notes | |-|-|-| | `0,2,4` | ニセモノ・ニセꜜモノ・ニセモノꜜ | | | `0 ,2, 4` | ニセモノ・ニセꜜモノ・ニセモノꜜ | The parser ignores all whitespace. | | `0,2,4` | ニセモノ・ニセꜜモノ・ニセモノꜜ | | !!! note "Restrictions on bolded numbers" Multiple numbers cannot be bolded together. If you want to bold multiple numbers, they have to be bolded individually. Additionally, commas cannot be bolded. For example, `0,1,2,3` is valid, but `0,1,2,3` and `0,1,2,3` are invalid. ## (2.2) PAOverride: Text Format {{ feature_version("0.11.0.0") }} ??? info "How To Type Special Characters (click here)" This section requires you to type certain special characters. You can type these characters on any standard IME. | Characters | Result | |:-:|:-:| | `\` { .smaller-table-row } | ＼ { .smaller-table-row } | | `うえ` (`ue`) { .smaller-table-row } | ￣ { .smaller-table-row } | | `,` { .smaller-table-row } | 、 { .smaller-table-row } | | `/` { .smaller-table-row } | ・ { .smaller-table-row } | If no number is found within the `PAOverride` field, the contents will be parsed using this format. To define any pitch accent in text format, use 「＼」 to specify downstep. For example, 人生 should be written as 「じ＼んせい」. For words with no downstep (平板型), the 「￣」 character must be placed at the end of the word. For example, 身長 should be written as 「しんちょう￣」. ??? info "Removing the required ￣ symbol (click here)" The restriction that 平板 words require the ￣ symbol at the end can be removed using the following {{ RTO }}: ```json "autoPitchAccent.paOverride.heibanMarkerRequired": false, ``` This would allow any words without any downstep marker to be rendered as 平板. Using the above example, one can instead type 身長 as 「しんちょう」. **Examples**: | PAOverride | Result | |-|-| | じ＼んせい | ジꜜンセイ | | いきお＼い | イキオꜜイ | | どうぐ＼ | ドウグꜜ | | しんちょう￣ | シンチョウ | ### Multiple Words Multiple words can be defined, as long as they are separated with either the 「・」 or 「、」 characters. This is particularly useful on expressions with multiple words, such as 「毒を食らわば皿まで」. **Examples**: | PAOverride | Result | |-|-| | どく＼、くらう￣、さら￣ | ドクꜜ、クラウ、サラ | | ち＼か・ちか＼ | チꜜカ・チカꜜ | !!! note This renderer will not accept any field with formatting. This means that bold, italics, overlines, etc. cannot be present in the field. For example, the input `にせもの` will be rejected. ## (2.3) PAOverride: Raw Text As a last case resort, if the input of this field cannot be parsed as either of the two, the exact contents of `PAOverride` will be displayed. This will behave exactly the same as `PAOverrideText`. --- # (3) PAPositions This field is automatically filled out as long as Yomichan has pitch accent dictionaries, and the tested word is covered in said dictionary. By default, the first pitch of the first dictionary is shown. ## Show All Possibilities in Dictionary {{ feature_version("0.11.0.0") }} TODO: update pictures with correct config + add new config value for all dictionaries Sometimes, pitch accent dictionaries show multiple pitch accents for a word. However, only the first pitch accent is shown by default. === "One entry (default)" {{ img("", "assets/autopa/papositions/one_unbolded.png") }} === "All entries" {{ img("", "assets/autopa/papositions/multiple_unbolded.png") }} === "One entry + bold" {{ img("", "assets/autopa/papositions/one_bolded.png") }} === "All entries + bold" {{ img("", "assets/autopa/papositions/multiple_bolded.png") }} If you want to show all of the pitch accent entries (in the first dictionary), use the following {{ RTO }}: ```json "autoPitchAccent.paPositions.displayMode": "selected-dictionary", ``` If you want to select the correct pitch accent, bold that position in `PAPositions` (or simply use `PAOverride` as described [above](#21-paoverride-positions-format)) !!! note This option only works on cards formatted with JPMN's `{jpmn-pitch-accent-positions}` helper. This means this option will not work on old cards that were imported to the `JPMN` format. --- # (4) AJTWordPitch If you have the optional [AJT Japanese](setupanki.md#ajt-japanese) add-on installed and correctly configured, then this field is automatically generated on all cards. This is used as a fallback option, in case your installed pitch accent dictionaries does not cover the tested content, but this add-on does. --- # How the Reading is Selected The reading consists of the actual kana that is shown on the card. By default, the word reading is selected based on the following priority: 1. `AJTWordPitch` 1. `WordReading` ## Reading: AJTWordPitch Usually, the reading is selected from `AJTWordPitch`. This has a few features over the raw word reading: * `AJTWordPitch` usually includes devoiced and nasal info, whereas `WordReading` does not. * Readings are katakana, and cannot be changed to hiragana. !!! note If you do not want the reading in `AJTWordPitch` to be used, change the following {{ RTO }} to `false`: ```json "autoPitchAccent.searchForAJTWord": false, ``` ## Reading: WordReading If the word cannot be found under `AJTWordPitch`, then the default reading in `WordReading` is used, and displayed in katakana. Unlike `AJTWordPitch`, this reading can be changed to the word reading kana (usually hiragana), katakana, or katakana with long vowel marks in the {{ RTO_FILE }}: ```json // The reading display to show if nothing is generated by AJT Japanese. // Valid options: // "word-reading" // "katakana" // "katakana-with-long-vowel-marks" "autoPitchAccent.readingDisplayMode": "katakana", ``` --- # Pitch Accent Styling Details This covers some details if you are directly using `PAOverrideText`, and want to have a similar format to the generated pitch accent. You very likely won't be doing this. ??? example "Styling Details (click here)" * The generated style is very similar to the generated style of the AJTWordPitch field. To display the style properly, you can simply copy and edit the HTML tags directly. If you want to see the true generated output, use the [AnkiWebView Inspector](https://ankiweb.net/shared/info/31746032) and inspect the element. * If you want to grey out other words, you will have to use the bold `` tag. However, you must wrap **the greyed out words** with the `` tag. This is the opposite of what would expect from everything in this page, but the behavior is this way due to restrictions in the current CSS specification. * Example with all possible styles: ```html チューカ°ꜜクセイ・チューカ°クꜜセイ ```