Skip to content
New 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

[fr] Incorrect translation for "Activation time" for extensions #1262

Open
Anthony-E-B opened this issue Jan 23, 2023 · 3 comments
Open

[fr] Incorrect translation for "Activation time" for extensions #1262

Anthony-E-B opened this issue Jan 23, 2023 · 3 comments
Labels
bug Issue identified by VS Code Team member as probable bug L10N
Milestone

Comments

@Anthony-E-B
Copy link

Anthony-E-B commented Jan 23, 2023

Type: Bug

Activation time is translated to Heure de l'activation, except it should be "Temps d'activation". They both translate from "Activation Time", but do not mean the same thing at all.
Visible in the extension panel when hovering the ms value, as well as any extension's details page( => État du runtime ("Heure de l'activation") )

Extension version: 1.74.12140928
VS Code version: Code 1.74.3 (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T16:59:02.252Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info
Item Value
CPUs 12th Gen Intel(R) Core(TM) i9-12900HK (20 x 2918)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Load (avg) undefined
Memory (System) 31.69GB (19.17GB free)
Process Argv . --crash-reporter-id 2d9b619b-faac-42cd-bc37-aa1f25714eef
Screen Reader no
VM 0%
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
vscccc:30610679
pyindex848:30577860
nodejswelcome1cf:30587006
282f8724:30602487
89544117:30613380
a9j8j154:30646983

@nmss
Copy link

nmss commented Mar 8, 2023

I encountered the same issue, here are some screenshots for context

image

image

@TylerLeonhardt TylerLeonhardt added bug Issue identified by VS Code Team member as probable bug L10N labels Oct 2, 2023
@TylerLeonhardt TylerLeonhardt added this to the Backlog milestone Oct 2, 2023
@cristianosuzuki77
Copy link

Tracking via 926531

@TylerLeonhardt
Copy link
Member

@cristianosuzuki77 any conclusion with this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug L10N
Projects
None yet
Development

No branches or pull requests

5 participants