Community
    • Login

    Notepad++ v8.4.9 Release Candidate 2

    Scheduled Pinned Locked Moved Announcements
    13 Posts 6 Posters 3.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • PeterJonesP
      PeterJones @schnurlos
      last edited by

      @schnurlos ,

      but I don’t know why.

      The right click menu is defined by contextMenu.xml. If you hadn’t blown away your AppData for v8.4.9-RC1 but you did blow it away for v8.4.9-RC2, then when you ran v8.4.9-RC2 it recreated a fresh contextMenu.xml, which is likely what fixed the connection between contextMenu.xml and the nativeLang.xml translations.

      Your contextMenu.xml was most likely out-of-date previously (which is why Don’s fresh test worked for him but your experience showed those lines weren’t translated.

      schnurlosS 1 Reply Last reply Reply Quote 3
      • schnurlosS
        schnurlos @PeterJones
        last edited by

        @PeterJones You’re right.
        But this could also happen to other users who like me always just upgrade without doing a complete reinstall … that is unfortunately a bit misleading.
        My “old” contextMenu.xml was dated 08-05-2021, the new one is from 01-17-2022.
        But thanks for that tip.

        1 Reply Last reply Reply Quote 0
        • donhoD
          donho @guy038
          last edited by

          @guy038
          Thank you for your heads up. Fixed now.

          The right click menu is defined by contextMenu.xml. If you hadn’t blown away your AppData for v8.4.9-RC1 but you did blow it away for v8.4.9-RC2, then when you ran v8.4.9-RC2 it recreated a fresh contextMenu.xml, which is likely what fixed the connection between contextMenu.xml and the nativeLang.xml translations.

          @schnurlos
          Just try to complete the above information provided by @PeterJones : In new version of contextMenu.xml, the attribute TranslateID has been added - this attribute and its value are necessary for the translation.

          1 Reply Last reply Reply Quote 4
          • PeterJonesP PeterJones referenced this topic on
          • Alan KilbornA
            Alan Kilborn
            last edited by Alan Kilborn

            Changing the localization away from the default of English seems to result in the tab-bar right-click context menu NOT being translated into the current localization’s language. It always remains in English even though the text on the rest of the Notepad++ UI has been changed into the selected localization.

            NOTE: This is simply with the default tab-bar context menu, no customization.

            NOTE: This is unrelated to “context menu” posts in this thread. Those were discussing editor window right-click context menu. Here’s I’m talking about when you right-click a file tab in the “tab bar”.

            donhoD Alan KilbornA 2 Replies Last reply Reply Quote 0
            • donhoD
              donho @Alan Kilborn
              last edited by

              @Alan-Kilborn
              Sorry, I don’t follow you?

              Lycan ThropeL 1 Reply Last reply Reply Quote 0
              • Lycan ThropeL
                Lycan Thrope @donho
                last edited by

                @donho ,
                I think @Alan-Kilborn is referring to the new tabContext menu. At least, it sounds like the new feature.

                1 Reply Last reply Reply Quote 0
                • donhoD donho unpinned this topic on
                • Alan KilbornA
                  Alan Kilborn @Alan Kilborn
                  last edited by

                  @Alan-Kilborn said in Notepad++ v8.4.9 Release Candidate 2:

                  Changing the localization away from the default of English seems to result in the tab-bar right-click context menu NOT being translated into the current localization’s language. It always remains in English even though the text on the rest of the Notepad++ UI has been changed into the selected localization.

                  It DOES work for these localizations:

                  • brazilian_portuguese, bulgarian, chineseSimplified, corsican, croatian, czech, english, french, german, japanese, polish, portuguese, russian, slovak, taiwaneseMandarin, turkish, ukrainian

                  But NOT for these:

                  • abkhazian, afrikaans, albanian, arabic, aragonese, aranese, azerbaijani, basque, belarusian, bengali, bosnian, breton, catalan, danish, dutch, esperanto, estonian, extremaduran, farsi, finnish, friulian, galician, georgian, greek, gujarati, hebrew, hindi, hongKongCantonese, hungarian, indonesian, irish, italian, kabyle, kannada, kazakh, korean, kurdish, kyrgyz, latvian, ligurian, lithuanian, luxembourgish, macedonian, malay, marathi, mongolian, nepali, norwegian, nynorsk, occitan, piglatin, punjabi, romanian, samogitian, sardinian, serbian, serbianCyrillic, sinhala, slovenian, spanish, spanish_ar, swedish, tagalog, tajikCyrillic, tamil, tatar, telugu, thai, urdu, uyghur, uzbek, uzbekCyrillic, venetian, vietnamese, welsh, zulu

                  I suppose it is just a matter of the translations “catching up”, but it seems like for the out-of-date ones that there is no new text for the UI, so it could have been autogenerated for the tab bar context menu, from the existing entries. In other words, why make the translators translate again something they’ve done once?

                  Example: Close on the File menu has a translation already. Close on the tab bar context menu could have been “ported” from the translation on the File menu:

                  7ad08deb-63da-4c8e-bf7f-52bc2f6e64f5-image.png

                  4c97dda4-f19e-48da-90cf-344675dd7f9a-image.png

                  1 Reply Last reply Reply Quote 2
                  • schnurlosS
                    schnurlos
                    last edited by

                    It seems that those translations where this is not working are just not up to date …
                    Just check f.e. the english.xml and the africaans.xml in the lokalization folder and search for text "<Item CMDID=“41003"”.
                    In my german.xml that text is translated and for this also working.

                    Alan KilbornA 1 Reply Last reply Reply Quote 0
                    • Alan KilbornA
                      Alan Kilborn @schnurlos
                      last edited by

                      @schnurlos said in Notepad++ v8.4.9 Release Candidate 2:

                      It seems that those translations where this is not working are just not up to date

                      Yes, I said this. I also said that there isn’t much of a reason for being out of date, as all translations (well, probably not “all”, but “most”) are known already.

                      schnurlosS 1 Reply Last reply Reply Quote 0
                      • schnurlosS
                        schnurlos @Alan Kilborn
                        last edited by

                        @Alan-Kilborn
                        That is part for the translators which (like me) are doing that for free:
                        https://community.notepad-plus-plus.org/category/6/translation
                        https://npp-user-manual.org/docs/binary-translation/
                        https://github.com/notepad-plus-plus/notepad-plus-plus/blob/master/PowerEditor/installer/nativeLang/afrikaans.xml

                        So if you want to update and share the africaans.xml just go ahead!

                        1 Reply Last reply Reply Quote 0
                        • PeterJonesP PeterJones locked this topic on
                        • First post
                          Last post
                        The Community of users of the Notepad++ text editor.
                        Powered by NodeBB | Contributors