Project

General

Profile

Actions

L10N_Bug #518

closed
YR

GLS NDSW JPN: New Driver - Update Driver - Translations out of context for [Install From Disk] pane

L10N_Bug #518: GLS NDSW JPN: New Driver - Update Driver - Translations out of context for [Install From Disk] pane

Added by Yoshimi Ray ja_JP 24 days ago. Updated 18 days ago.

Status:
Known Defect
Priority:
Medium
Assignee:
-
Error Type:
Linguistic
Test Case:
New Driver
Test Run:
Language:
ja_JP
Source String:

Install From Disk

Insert the manufacture's installation disk, and then make sure that the correct drive is selected below.

Copy manufacture's files from:

Current Translation:

フロッピーディスクからインストール

製造元が配布するインストール ディスクを指定したドライブに挿入して、下の正しいドライブが選択されていることを確認してください。

製造元のファイルのコピー元(C):

Suggested Translation:

ディスクからインストール

製造元のインストール・ディスクを挿入し、以下で適切なドライブが選択されていることを確認してください。

製造元ファイルの場所(C):

Back Translation:

Description

Issue summary: New Driver - Update Driver - Translations out of context for [Install From Disk] pane. Also "Disk" is mistranslated as "Floppy Disk", and the transliteration of "installation disk" is missing Nakaguro, violating Intel JP Style Guide. Suggested texts also fix a couple of awkward grammar issues.

Steps to reproduce:
Launch File Explorer.
In the build folder, navigate to APPS\SETUP\SETUPBD\Winx64, and click SetupBD.exe.
Check the pop-up message.
Click OK and check the installation.
Open Device Manager
Open Properties of the FLV NIC: Intel® Ethernet Network Adapter X710-TL
In the Driver tab, click Update Driver button
Click Browse my computer for drivers (second option)
Click Let me pick from a list of available drivers on my computer (second option)
See the issues.

Expected result:
[Text 1]
ENU: Install From Disk
JPN: ディスクからインストール

[Text 2]
ENU: Insert the manufacture's installation disk, and then make sure that the correct drive is selected below.
JPN: 製造元のインストール・ディスクを挿入し、以下で適切なドライブが選択されていることを確認してください。

[Text 3]
ENU: Copy manufacture's files from:
JPN: 製造元ファイルの場所(C):

Actual result:
[Text 1]
ENU: Install From Disk
JPN: フロッピーディスクからインストール

[Text 2]
ENU: Insert the manufacture's installation disk, and then make sure that the correct drive is selected below.
JPN: 製造元が配布するインストール ディスクを指定したドライブに挿入して、下の正しいドライブが選択されていることを確認してください。

[Text 3]
ENU: Copy manufacture's files from:
JPN: 製造元のファイルのコピー元(C):

HW configuration: Carlsville (FVL)
SW configuration: TIC-741971_VC61875 / Windows 11 22H2

Operating System: Windows 11 22H2 x64


Files

JPN_NewDriver_D12.png (115 KB) JPN_NewDriver_D12.png Yoshimi Ray ja_JP, 04/05/2026 12:17 AM
JPN_NewDriver_D12.png

Related issues 1 (0 open1 closed)

Related to NEX - L10N_Bug #517: GLS NDSW JPN: New Driver - Update Driver - translations out of context for [Browse for drivers on your computer] paneKnown DefectActions

YR Updated by Yoshimi Ray ja_JP 23 days ago Actions #1

Two required steps were missing:

Steps to reproduce:

  1. Launch File Explorer.
  2. In the build folder, navigate to APPS\SETUP\SETUPBD\Winx64, and click SetupBD.exe.
  3. Check the pop-up message.
  4. Click OK and check the installation.
  5. Open Device Manager
  6. Open Properties of the FLV NIC: Intel® Ethernet Network Adapter X710-TL
  7. In the Driver tab, click Update Driver button
  8. Click Browse my computer for drivers (second option)
  9. Click Let me pick from a list of available drivers on my computer (second option)
  10. Click Have Disk... button
  11. Click Browse... button
  12. See the issues.

JD Updated by Javier Domingo 22 days ago Actions #2

  • Status changed from New to Confirmed

TT Updated by Terence Tsang 21 days ago Actions #3

  • Related to L10N_Bug #517: GLS NDSW JPN: New Driver - Update Driver - translations out of context for [Browse for drivers on your computer] pane added

TT Updated by Terence Tsang 21 days ago Actions #4

  • Status changed from Confirmed to Need More Info
  • Assignee set to Javier Domingo

@Javier Domingo Same as ticket 517.

These strings are not in our files, because they are part of the Windows OS strings for the Device Manager application. We have no control over these translations as they are part of the OS. I am curious to understand if the reported issues are critical because I would assume Microsoft went through a certain layer of review/approval for the current strings.

Is this really something we've never encountered before either?

TT Updated by Terence Tsang 21 days ago Actions #5

  • Status changed from Need More Info to Investigating

JD Updated by Javier Domingo 18 days ago Actions #6

  • Status changed from Investigating to Known Defect

JD Updated by Javier Domingo 18 days ago Actions #7

  • Assignee deleted (Javier Domingo)
Actions

Also available in: PDF Atom