phibr0 / obsidian-dictionary Public
generated from obsidianmd/obsidian-sample-pluginNew issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Pronunciation' and 'Meanings' not translated #16
Comments
|
I currently can't check in App, could you provide Screenshots or just explain where exactly something isn't translated? As I am checking in the Code it should all be translated fine. |
|
Let’s take the phrases 'Pronunciation', 'Meanings' and 'New Note', which are used in the side panel and when generating a new note (for Let’s also assume we’re using only English and German. The phrases are correct in //dictionaryView.svelte
'Enter a word': 'Gebe ein Wort ein',
'Pronunciation': 'Aussprache',
'Meanings': 'Bedeutungen',
'New Note': 'Neue Notiz',When setting Obsidian to German ("Deutsch"), the side panel still shows the English headings: When I click on 'New Note', the English headings are also used in the new note: |
|
The Language is set by Obsidians internal Moment Locale. You have set your Language to German which should turn the Plugins Language to German too. Are the Settings also all in English? |
|
The Obsidian settings are in German, those of non-translated plugins in English, yours also in English: Reminds me of an odd problem I had, and nobody found an answer for (I’m using the moment.js locale myself to check what language Obsidian runs in): https://forum.obsidian.md/t/new-with-0-12-4-moment-locale-sticks-at-en-even-when-i-switch-obsidian-to-another-language/19673 |
|
Hm. If I enter moment().locale()in the dev console, it gives me Let me try moment.locale("de")and see what happens. Still the same: But I wonder … if it wouldn’t work in general, why then did it translate |
|
"Adjektiv" came as part of the API Response, not from the Plugin itself. Could you maybe try to disable all Plugins except the Dictionary Plugin? Or just create a Test Vault with only that Plugin installed. |
|
Also I am pretty sure that after setting the moment locale to de the View needs to be re-rendered to show changes in these Strings. |
|
Yep, I’ve later seen that it came from the API. Any idea how I could re-render the view? I’ll try the plugin disable/new vault later on. |
|
I think just closing it (right click on the icon) and opening it again with the Command should work |
|
Got it! After disabling all plugins except yours, …
So I must really dig in deeper to isolate the plugin that causes the locale mess-up. Sorry for bothering you with this!
Btw, thanks for making this really useful plugin, and actually taking care of translations—not many plugins do that. |
|
The I think the Calendar Plugin overrides the moment locale but I am not sure. |
|
Calendar: Yeah, someone mentioned that in the forums, but I’ve never used that. So there must be another miscreant ;-) Doesn’t the note always contain all information, even if there’s nothing in it? If not, we have another minor bug. |
|
Since this isn't really a Issue of this Plugin i will close this for now. The other Plugins which are localized also get the locale from moment which is why I think it's fine like that. |
|
Yep. I finally found the miscreant: It was the Obsidian Pomodoro Plugin that globally set the |





The headers 'Pronunciation' and 'Meanings' aren’t translated, and 'New Note' isn’t. All are in 'de.ts', for example.
The text was updated successfully, but these errors were encountered: