I don't think there're any.
But I think there should be a system (maybe an API or sth.) for plugins, so
that official plugins can be translated fully and an author of a unofficial
plugin can decide whether necessary or not. Just like Sourcemod Plugins
<https://wiki.alliedmods.net/Translations_(SourceMod_Scripting)>, there is
a "translation" folder with translation files one by one (a plugin can
decide which to use).
Further more, it would be even better if an author of a plugin can use
existed-translation/glossary table which I mean they can use some of
audacity original translation for strings or even glossarys.
scootergrisen <[email protected]>于2017年9月5日周二 下午8:30写道：
> Menu item strings in the Analyze menu are not translatable.
> Like "Beat Finder..." to "Sound Finder...".
> Same for the bottom menu item in generate and effects menu.
>
> I guess its comming from files in /Plug-Ins/ folder.
> Like Plug-Ins/beat.py have:
> ;name "Beat Finder..."
>
> Are there perhaps any way to get this translated for at more complete
> translation for the user?
>
> Perhaps something like:
> ;name "Beat Finder..."
> ;name[da] "Taktfinder..."
> ;name[sv] "Nogetfinder..."
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-translation mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/audacity-translation
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-translation mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-translation
