Opened 9 years ago

Closed 6 years ago

#7162 closed enhancement (fixed)

A bitsinfo localization

Reported by: Karvjorm Owned by: nielx
Priority: normal Milestone: R1
Component: Kits/Translation Kit Version: R1/alpha2
Keywords: bitsinfo localization patch Cc: Karvjorm
Blocked By: Blocking:
Has a Patch: yes Platform: All

Description

Here is src/tools/translation/bitsinfo localization. I added also a resource file for the program.

Attachments (1)

bitsinfo-localization.patch (5.9 KB ) - added by Karvjorm 9 years ago.
A bitsinfo localization patch

Download all attachments as: .zip

Change History (10)

by Karvjorm, 9 years ago

Attachment: bitsinfo-localization.patch added

A bitsinfo localization patch

comment:1 by Karvjorm, 9 years ago

Has a Patch: set

comment:2 by axeld, 9 years ago

While your localization enthusiasm is really appreciated, I think localizing tools like this (especially if they don't originate from us) is just a waste of time. Does it even show up on the image?

While I personally don't like translated shell commands, there are probably a lot of those that haven't been translated yet, hint, hint :-)

in reply to:  2 comment:3 by Karvjorm, 9 years ago

Replying to axeld:

While your localization enthusiasm is really appreciated, I think localizing tools like this (especially if they don't originate from us) is just a waste of time. Does it even show up on the image?

While I personally don't like translated shell commands, there are probably a lot of those that haven't been translated yet, hint, hint :-)

Those bitsinfo, pnginfo, bmpinfo programs can be found under /srs/tools/translation/ as well as Inspector Translation Program (http://hta.polytect.org/catalogs/view/133/fi). I personally think that also programs that can be run in the Terminal window should be localized as well the desktop program's messages that are printed in the Terminal window when they are run from the command line. I'm making them available and others can make decisions, if some specific localization is taken with the distribution image, or not.

Br, Karvjorm

comment:4 by axeld, 9 years ago

It's certainly your time, and your reasoning is sound indeed :-)

comment:5 by humdinger, 9 years ago

Just a small reminder: Some commandline apps' in/output strings may be used in scripts. One has to be careful what's going to be translated. The usage/help output should be save at least... :)

in reply to:  5 comment:6 by zooey, 9 years ago

Replying to humdinger:

Just a small reminder: Some commandline apps' in/output strings may be used in scripts. One has to be careful what's going to be translated. The usage/help output should be save at least... :)

But it's virtually impossible to decide what input/output might be used by scripts. As a result, I wouldn't put the burden on the commandline tool being translated but on the calling script instead. That script should set LC_ALL=POSIX before invoking any command that it wishes to analyze.

comment:7 by nielx, 7 years ago

Owner: changed from nobody to nielx
Status: newin-progress

Per comment:18 and comment:20, I will review the patches and push them upstream.

comment:8 by nielx, 7 years ago

Component: - GeneralKits/Translation Kit

comment:9 by nielx, 6 years ago

Resolution: fixed
Status: in-progressclosed
Note: See TracTickets for help on using tickets.