I don’t know how to do anything with furigana, but I’d be willing to look into it to help you since I do know a bit about anki. However, before I (or you) invest any time in solving this problem, you should be sure you actually want it solved.

Why show furigana at all? What is the goal of the card in question? Are you trying to learn the words in the sentence (一人, in this case)? If so, I would recommend leaving the furigana off. That forces you to remember the meaning and reading of the word, which is more useful that the meaning on it’s own. This is especially true for very basic vocabulary which will never have furigana in native material.

If the point of the card is to practice a grammar point (A は B です。, in this case), I would suggest only using words in the sentence that you already know (meaning and reading). In which case, the furigana is superfluous.

If you’re dead set on getting the furigana fixed though, I’ll need you to answer these two questions:
Where are you importing the decks from?
What are you using to show furigana?

There’s a lot of background info here. To fix the problem, jump to TLDR.

There is a pluggin called “Japanese Support” which this site used to recommend you install. However it seems most of the functionality of that pluggin was integrated into Anki 2.

One of the features of that plugin (that has not been made native to the main product) is that note types containing “Japanese” anywhere in their name and that contain the fields “Expression” and “Reading” will be able to automatically generate readings (furigana) in the “Reading” filed for anything typed into the “Expression” field. The way this seems to have worked is that the “Expression” field was broken down into parts and each part compared to a table of some kind that contained readings. The contents of the “Expression” field were then copied into the “Reading” filed with each part being separated by a space (an “English” space not a “Japanese” space). Any readings found previously are then added after their respective parts from the original and wrapped in brackets. See below:

Expression: 私は忙しい
私は忙しい –> 私＋は＋忙＋しい –> (look up readings) –>
In Reading filed: 私[わたし]<english space>は<english space>忙[いそが]<english space>しい

The readings (the stuff in brackets) are then centered over the areas between the English spaces. That is to say that わたし is centered between the start of the field and the first space, nothing is centered between the first and second spaces (since there was no bracketed reading), いそが is centered between the second and third space, and nothing is centered between the third space and the end (again, since there was no bracketed reading).
The end result is that わたし is right above 私 and いそが is right above 忙, right where they should be. You can mess things up though by going into the “Reading” field and adding, deleting or moving the English spaces around.
Why would anyone do that? Because the readings that are generated automatically are not always correct. 一人 for example is not automatically matched to ひとり. So, if you have that word in your expression, you need to manually correct the stuff that gets put between the brackets.
It’s my guess that when the deck was being made, and when that correction was being made, the deck’s creator accidentally deleted one of the English spaces so that the reading no longer centered correctly. And I’m guessing that the missing space went unnoticed because it is so small compared to Japanese style spaces which this site uses in it’s sentences.

TLDR:
To fix the problem, type an English space (that is hit the spacebar while typing in English, not Japanese) before “一人” in the Reading field of the card.

—whew—

• This reply was modified 9 years ago by  thisiskyle.
• This reply was modified 9 years ago by  thisiskyle.
• This reply was modified 9 years ago by  thisiskyle.