Sophia Community
Replies: 3 comments
-
|
Hello! Glad to see you here, and we appreciate your effort to help with the translation. Let’s take the first function that has ID 100: All you need it to add new „DE“ strings. Look: {
"Id": 100,
"Header": {
"EN": "The telemetry service",
"RU": "Служба телеметрии",
"DE": "Der Telemetrie-Dienst"
},
"Description": {
"EN": "Configure the Connected User Experiences and Telemetry (DiagTrack) service, and connection for the Unified Telemetry Client Outbound Traffic",
"RU": "Настроить cлужбу \"Функциональные возможности для подключенных пользователей и телеметрия\" (DiagTrack) и соединение для исходящего трафика клиента единой телеметрии",
"DE": "Konfigurieren Sie den Dienst Connected User Experiences and Telemetry (DiagTrack) und die Verbindung für den ausgehenden Verkehr des Unified Telemetry Client"
},
"Type": "CheckBox",
"Tag": "Privacy"
}As I wrote in the comments, we've understood that if the file grows bigger it will look like a mess, so need to split it into languages to make the traslation process easier. Unfortuanately, we aren't confident that the current description sections is finished. I make changes to it from time to time. I think in a month or so I'll finish it up, and you may start translating.
You're right, but in this case, if there is no translatable description, the entry will be empty,because the parse engine wasn't able to find it. Every translation has to have its' separate file to parse.
I've heard it for the first time. Seriously )). Well, I have not words. But we've already started working out 2.0. I want SophiApp 2.0 to follow the Windows 11 UI guidelines. Look at Windows Terminal 1.13 Settings UI or Power Toys: Does this UI look ugly for your too? 🐱 |
Beta Was this translation helpful? Give feedback.
-
|
I am aware of how JSONs work and I know that another language-specific XML is required. I just wasn't sure if a translation is required if it matches the English original phrase. But thanks for the clarification. 👍 The layout of the current design is alright but the color is really weird. I am also fine with the design of the current Script Wrapper. |
Beta Was this translation helpful? Give feedback.
-
Hello!
DeskModder once again had an article about SophiApp. I know you've seen it because I read all the comments.
To close the gap caused by the language barrier of the article, I would like to start a discussion here.
I am a native German speaker and follower of the DeskModder blog. I am also a long-time SophiScript user and am currently waiting for Windows 11 support of the SophiApp. The script was always a big help when setting up new systems. So thanks for that!
I think the main arguments of people replying here were the UI of the app and the translation.
About the translation:
I know you're offering that people can translate the app. I can submit a German translation but I have one question beforehand.
Is a German translation in the
UIData.jsonneeded if the German string would match the English string? I am used to XML string tables or Fluent. Usually, if a specific language doesn't have an entry for a string, it will fall back to English. If the string of the German language matches the English one, a translation wouldn't be necessary.About the UI:
I am not a big fan of the UI either. It's a pretty ugly app (sorry). But that's just my personal opinion and it's my personal preference. But I see some of the people in the comments agree. This shouldn't be much of an issue though because, in the end, it's the app's functionality that matters. Is a UI rework planned in the future? I wouldn't mind if you just focus on functionality, bug fixing and most importantly OS support.
Beta Was this translation helpful? Give feedback.
All reactions