I'm trying to create Japanese translate xml file, but there are unclear point

[shinobifuku]

Hello,

I am creating a Japanese XML file for Secure Exam Browser. It is almost complete, but I am having trouble with two entries because the original English display text is unclear, and I cannot translate them into appropriate Japanese.

Target labels:
ProctoringFinalizationDialog_StatusAndTime
ProctoringFinalizationDialog_StatusWaitingAndTime

Unclear point:
Both labels use the variable %%TIME%%. What exactly is displayed by this variable? Is it the current time?

And what filename is appropriate for xml file for Japanese translation?

[dbuechel]

Thank you very much in advance, that's fantastic news! The variable %%_TIME_%% displays the point in time when a resp. the transmission operation(s) will be resumed during the finalization of the screen proctoring functionality, e.g.:

ProctoringFinalizationDialog_StatusAndTime: "Waiting to execute transmission operation 4 of 10 at 12:00:30..."
ProctoringFinalizationDialog_StatusWaitingAndTime: "Waiting to resume 16 transmission operations at 14:20:15..."

The filename should be the two-letter ISO language name for Japanese, which according to the list of ISO 639 language codes would be ja.xml.

[shinobifuku]

Hello,

Thank you for your reply.
Based on your explanation, I will think about appropriate Japanese translations for the two labels.

By the way, how should I deliver the XML file I created to you?

P.S.
From questions and answers by other users in a separate thread, I understand that a multilingual mechanism for the Config Tool has not been implemented at this time. However, I would like to let you know that we, users in the Japanese-speaking community, believe it would be wonderful if this feature were implemented.

[shinobifuku]

Hello.

I have created the jp.xml file. The character encoding is UTF-8 (with BOM), line endings are LF (UNIX), and the format matches that of en.xml.

I am attaching ja.zip, which contains the compressed ja.xml file., so please review its contents.

ja.zip

For translating from the original English to Japanese, I first performed a batch translation using ChatGPT to improve efficiency, avoid typos, and ensure terminology consistency. I then manually reviewed all entries against the original text and corrected any parts that seemed inappropriate. In a few places where a literal translation would be unclear, I used a more natural paraphrase instead.

日本人（日本語）ユーザーへ。
原文（英語）から日本語への翻訳は、作業の効率化とタイプミスの回避、用語の統一などの観点から、まずChatGPTで一括翻訳をしました。しかし、全ての項目について、原文と日本語文のチェックを目視で行い、適切でないと思われる個所は修正しました。原文の直訳では意味が通りにくい箇所が数か所あったので、そこは意訳にしています。

[shinobifuku]

Hello, @dbuechel .

About ten days ago, I submitted a Japanese translation file (ja.xml) based on en.xml. Were there any issues with the format or content? If there are any mistakes, I would be happy to fix them, so I would appreciate it if you could let me know the results of your review.

Also, in a previous thread about other language versions, I saw a comment mentioning that a different approach is required for the macOS version. I would like to help with adding Japanese language support for the macOS version as well. My understanding is that, unlike Windows, macOS (the modern versions since Mac OS X, not the classic Mac OS) has built-in mechanisms for OS- and application-level localization. If the application is developed following standard conventions, it should be possible to achieve basic localization simply by adding the appropriate language resource files and rebuilding the application. Please let me know how I could contribute on this front as well.

Thank you very much.

[dbuechel]

Terribly sorry for the late reply, I have just recently returned from vacation and am just about to catch up on everything that happened while I was away. Thank you very much for your contribution, it is indeed highly appreciated!

The raw file provided above should be perfectly fine, I'll definitely try to integrate it later on this week and will let you know once there is a development build ready for testing. Thanks again for your contribution!

[dbuechel]

Regarding the configuration tool: We'll definitely implement localization for the configuration tool once we were able to refactor it - the current legacy implementation will unfortunately remain hard-coded in English, as our primary goal is to first rewrite it as mentioned.

With respect to a translation of the macOS & iOS versions, I'd kindly ask you to inquire the required format directly in the respective repository, e.g. via https://github.com/SafeExamBrowser/seb-mac/discussions.

[dbuechel]

Again sorry for the delay, we're currently (as is unfortunately often the case) very occupied with internal priorities. I have just integrated your translation, please do feel free to test it in the latest development build of version 3.11.0: https://sebdev.ethz.ch/api/buildjobs/g9am53nvk9gupp5t/artifacts/SEB_3.11.0.875_SetupBundle.exe.

Thanks again for the most valuable contribution, it is highly appreciated!

[shinobifuku]

Hi. I tested it.
In the splash window at startup, as well as in all interface elements and areas where messages are displayed, messages such as:

Could not find text for key 'MessageBox_ApplicationAutoTerminationDataLossWarning'!

are shown, indicating that the text corresponding to the key could not be found.
As a result, neither the expected Japanese messages nor the original English messages are displayed.
I tested this by installing it on three different Windows 11 PCs, and the same issue occurred on all of them. Just to be safe, I uninstalled any existing installation of Safe Exam Browser before installing it.

Of course, the display language is set to “Japanese,” the country or region is set to “Japan,” and the device setup region is also set to “Japan,” which are the standard settings for a Windows PC used in Japan.

[shinobifuku]

@dbuechel

I believe there was a mistake in the XML file I created.
In each entry, the attribute should be written as Entry key= with a lowercase key, but in my file it was written as Entry Key= with an uppercase K.
I sincerely apologize for the oversight.

I am resubmitting the corrected ja.xml file.

ja.xml.zip

[dbuechel]

Aha I see, excellent; I shall update the file this week and provide another build for testing. Most unfortunately, the current implementation is (too) strict regarding such details - I'll see whether I can change that quickly or otherwise create an internal issue to do so later on.