Translation Feedback - Japanese

keith's Avatar

keith

29 Sep, 2017 08:06 AM

Please keep all feedback pertaining to the Japanese translation of Scrivener's UI to this thread.

NOTE: Please try to explain all issues in English, as we only speak English ourselves, although we will be passing all feedback on to our translators.

Thanks!

HOW TO POST FEEDBACK

When posting suggestions for changing translations, I would be grateful if you could do it in this format from now on:

++ Place in Interface

"Current Translation" = "Suggestion"

"Another Translation" = "Another Suggestion"

For instance:

++ Main Menu:

"Navigation" = "Blah Blah"

"Outliner Options" = "Blah blah"

++ Inspector:

"Comments" = "Better Word"

++ Compile:

"Compile" = "Suggestion"

And so on. This will allow me to copy your suggestions straight into my new updating tools with very little editing and so ensure they are applied. If you would rather send me a file with all the suggestions, please just use the above format and put it into a plain text file. Thanks!

  1. Support Staff 1 Posted by keith on 29 Sep, 2017 08:21 AM

    keith's Avatar

    A new beta is going out today in which the entire UI has been translated. (Please note that the tutorial and documentation are not translated.) Because Scrivener has been evolving a little during the translation period, there may well be a few phrases or words that are still in English because they changed or were added to Scrivener while the translators were working. Please let us know all problems you find, including any phrases you find that are still in English.

    Thanks!

  2. 2 Posted by mukairyoji on 06 Oct, 2017 10:58 AM

    mukairyoji's Avatar

    Hello,
    I reviewed beta 13.
    First, I checked Japanese translations in pull-down menu. Look the attached file please.
    I will continue to check. Thank you.

  3. 3 Posted by mukairyoji on 07 Oct, 2017 05:50 AM

    mukairyoji's Avatar

    Hello,
    I reviewed the main window of beta 13.
    Please see the XLSX and PNG together.

  4. Support Staff 4 Posted by keith on 20 Oct, 2017 05:21 PM

    keith's Avatar

    Many thanks for all of this feedback! I have done my best to incorporate all of this into the next update.

  5. Support Staff 5 Posted by keith on 20 Oct, 2017 06:45 PM

    keith's Avatar

    HOW TO POST FEEDBACK

    When posting suggestions for changing translations, I would be grateful if you could do it in this format from now on:

    ++ Place in Interface

    "Current Translation" = "Suggestion"

    "Another Translation" = "Another Suggestion"

    For instance:

    ++ Main Menu:

    "Navigation" = "Blah Blah"

    "Outliner Options" = "Blah blah"

    ++ Inspector:

    "Comments" = "Better Word"

    ++ Compile:

    "Compile" = "Suggestion"

    And so on. This will allow me to copy your suggestions straight into my new updating tools with very little editing and so ensure they are applied. If you would rather send me a file with all the suggestions, please just use the above format and put it into a plain text file. Thanks!

  6. 6 Posted by Martin on 23 Oct, 2017 08:43 AM

    Martin's Avatar

    Reply to: Posted by mukairyoji on Oct 07, 2017 @ 06:50 AM

    1. 構成 is wrong interpretation for "composition" which should be here 執筆

      • 3 is wrong interpretation of "words" and "chars" which means 単語数 and 文字数 

    This part of the menu should look like this:

    単語数:

    文字数:

    文字数(スペースなし):

    段落数:

    文数:

    平均段落長さ:

    平均の文長さ:

    1. NO style --> スタイルなし

    it is hard to interpret this string as a message to the user, simply "using no style" is meant.//

    Image Name

  7. 7 Posted by Martin on 23 Oct, 2017 08:46 AM

    Martin's Avatar

    Reply to: Posted by mukairyoji on Oct 07, 2017 @ 06:50 AM

  8. 8 Posted by Martin on 23 Oct, 2017 08:50 AM

    Martin's Avatar

    Reply to: Posted by mukairyoji on Oct 06, 2017 @ 11:58 AM

  9. 9 Posted by mukairyoji on 24 Oct, 2017 05:02 AM

    mukairyoji's Avatar

    Hello Martin,
    I checked "Translator_-_mainWindow_beta13-fixed.xls".
    I think the fixed work is very good.
    Thank you!

  10. 10 Posted by Martin on 24 Oct, 2017 10:35 AM

    Martin's Avatar

    That's great news, thanks for your help!

  11. 11 Posted by mukairyoji on 24 Oct, 2017 11:21 AM

    mukairyoji's Avatar

    Hello Martin,
    I checked "Translator_-_Scrivener_beta_13-fixed.xls".
    I have added new comments in XLS as new colum "Reply from tester".

  12. 12 Posted by Martin on 24 Oct, 2017 11:51 AM

    Martin's Avatar

    Thanks, I have passed this onto the translator.

  13. 13 Posted by Martin on 26 Oct, 2017 03:46 PM

    Martin's Avatar

    From the translator. I did reply on email as well so sorry if this comes through twice.

  14. 14 Posted by mukairyoji on 27 Oct, 2017 12:00 PM

    mukairyoji's Avatar

    Hello Martin,
    I reviewd "Scrivener_beta_13-fixed.xls", there is only one issue left.
    Please see the attatched XLS. Thanks!

  15. 15 Posted by Martin on 30 Oct, 2017 02:38 PM

    Martin's Avatar

    Hello Martin, I reviewd "Scrivener_beta_13-fixed.xls", there is only one issue left. Please see the attatched XLS. Thanks!

    I have informed the translator, I will report back shortly.

  16. 16 Posted by Martin on 02 Nov, 2017 05:23 PM

    Martin's Avatar

    Hello Martin, I reviewd "Scrivener_beta_13-fixed.xls", there is only one issue left. Please see the attatched XLS. Thanks!

    The Japanese translator has asked is it just the yellow shaded cells?

  17. 17 Posted by mukairyoji on 03 Nov, 2017 06:06 AM

    mukairyoji's Avatar

    Hello,
    The only one issue is the blue shaded cell (see bottom right in XLS).
    I write the same content below:

    ++ (xliff 3266 ?)
    (...may lead to unexpected effects with different formats sharing the same section layout and front and back matter settings.)
    ”また、異なる形式が同じセクションレイアウトとフォント、後付設定を共有すると想定外の結果につながることがあります。”
    =
    "また、異なるフォーマットを、同じセクションレイアウトと前付け/後付けで共有すると、想定外の影響を与えることがあります。"

    ( "フォント" in the current translation looks misunderstanding of "front" )

  18. 18 Posted by Martin on 10 Nov, 2017 10:45 AM

    Martin's Avatar

    The only one issue is the blue shaded cell (see bottom right in XLS).

    New file attached from the translator.

  19. 19 Posted by mukairyoji on 10 Nov, 2017 12:01 PM

    mukairyoji's Avatar

    Hello,
    According to "Scrivener_beta_13-fixed2-Oct27 (2).xlsx", the issues that I reported in this XLS are all fixed.
    I will wait for the next beta. Thanks.

  20. 20 Posted by Martin on 13 Nov, 2017 12:17 PM

    Martin's Avatar

    According to "Scrivener_beta_13-fixed2-Oct27 (2).xlsx", the issues that I reported in this XLS are all fixed.

    Hi mukairyoji,

    I have now created an import file to correct the translations on the spreadsheets we have been working on. Can you have a quick check to make sure the English corresponds with the recommended translations you and the translator have agreed on.

    I had to piece it all back together into the format you see attached which wasn't an easy task.

    Thanks

    Martin

  21. 21 Posted by mukairyoji on 14 Nov, 2017 04:13 AM

    mukairyoji's Avatar

    Hello Martin,

    Many issues have been fixed by the XLS files that were exchanged in the past.
    I'm afraid, it seems that some issues have not been applied in this TXT.
    Please check this attached file. I added some comments after the characters "//".
    I did not add a line break or delete it. It will be better to use diff. Thanks.

  22. 22 Posted by mukairyoji on 22 Nov, 2017 02:00 PM

    mukairyoji's Avatar

    Hello Martin, all the developers of L&L,
    First of all, congratulations on releasing of version 3!
    A lot of Japanese users (and users in the future) are very very welcome to Japanese interface and vertical layout.
    I was surprised that iOS version was also translated into Japanese. Very thank you for your hard work!

    Now, I have got v3.0 for macOS, v1.1.4 for iOS, and v3.0 beta 1 for Windows.
    I discovered that translation work looks still in progress. Some issues which I had reported does not applied.
    May I still submit reports of translation here? Thank you.

  23. 23 Posted by Martin on 22 Nov, 2017 02:04 PM

    Martin's Avatar

    That's great, I will get the changes applied shortly. Thanks for all your help as well.

  24. 24 Posted by Martin on 27 Nov, 2017 01:51 PM

    Martin's Avatar

    21 Posted by mukairyoji on Nov 14, 2017 @ 04:13 AM

    I have removed the comments from the file you attached on here. Please can you have a final look over it before I send it to Keith for the next update.

  25. 25 Posted by mukairyoji on 27 Nov, 2017 02:51 PM

    mukairyoji's Avatar

    Hello,
    I checked "Japanese_Updated_27.11.2017.txt".
    There is only one issue left below.
    As a precaution, I attach the file that I fixed. Thanks.

    DocumentView.strings
    ----------------------
    "New Folder From Selection" = "選択項目から新しいフォルダを作成"
    (in the txt, was "選択から新しいフォルダを作成")

  26. 26 Posted by Martin on 27 Nov, 2017 02:59 PM

    Martin's Avatar

    Thanks, I will get this sent over to Keith.

  27. 27 Posted by mukairyoji on 08 Dec, 2017 02:38 AM

    mukairyoji's Avatar

    Hello Martin,
    May I report translation issues of iOS version 1.1.15 in this thread?

    All issues are in compile option settings.

    ++ Picture 1 (the first window to compile)
    Current: "保存オプション" <--Japanese users will mis-understand that "open the options window to save file"
    Suggestion: "オプションを保存"

    ++ Piture 2 (the window to select file format)
    Current: "単語"
    Suggestion: "Word" or "DOCX" <-- "Word" is the product name. No need to translate.

    ++ Picture 3 [1] (the window to select paper size)
    Current: "文字"
    Suggestion: "レター" <-- Habitual name in Japan

    ++ Picture 3 [2]
    Current: "法務"
    Suggestion* "リーガル" <-- Habitual name in Japan

  28. System closed this discussion on 02 Feb, 2018 02:40 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac