#6318: Fixing listport output and changing it to a localized BApplication --------------------------+------------------------------------------------- Reporter: Karvjorm | Owner: pulkomandy Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: - General | Version: R1/alpha2 Resolution: | Keywords: listport localization Blocked By: | Has a Patch: 1 Platform: All | Blocking: --------------------------+------------------------------------------------- Comment (by Karvjorm): Replying to [comment:6 axeld]: > First of all, thanks for your thorough reply! > > Replying to [comment:5 Karvjorm]: > > Replying to [comment:4 axeld]: > > > I'm against applying this patch for the following reasons: > > > * listport is a very simple command, there is no reason to move it into its own subdirectory > > There are also some other commands with subdirectories, as ideinfo, listdev and playsound. > > Usually because they need some special private headers. In general, though, localization is not a good reason to them into a separate directory, because then all command line tools would need to be in one. Instead, we should develop a way to simplify mass localization of the command line tools in the "bin" directory using some additional Jam magic. Of course, this should be done as the first step to localize the command line apps. > > Aren't there any GUI apps to be localized first? ;-) Yes, but because HTA is offline, I'm not absolute sure which GUIs are already localized. For example, I made a part of filepanel localization (in src/bin) and someone else had done other part of filepanel localization. So I have waited for the updates for the development environment. > > Anyway, your persistence and motivation to work on localization is very much appreciated, please don't get me wrong. > > > One advantage with a subdirectory is that you can include also a resource file with app_flags. Before defining application as a B_BACKGROUND_APP (or whatever it was) the new BApplication application popped up in the deskbar once during each run and then disappeared immediately. > > As you already write, this issue has been fixed long ago :-) > > > > * it's called "listport", not ListPort, so the source file should match > > That's right, but you can easily fix this by changing "Application listport" and "DoCatalogs listport" to Jamfile. I used this form to be sure that the applications do not be mixed during the "evaluation period". > > Not sure what you mean by that. At present you can find in my src/bin/lisport/Jamfile file lines like "Application ListPort" and "DoCatalogs ListPort". But if I (or you) change it to "Application listport", we have '''listport''' executable generated (not ListPort executable) in generated/objects/.. etc. > > > Command line applications are localized in Linux and I like it. You can easily change locale settings to English, if you want to use English command line commands. > > Same for the other direction :-) > Having english command line tools by default has the added advantage that when you share stuff with others (be it in a bug tracker, or a forum) everything will use the same language. It also helps with writing scripts. It is not so big problem in Linux. For example, if you as a developer received an error message with the localized text like "tiedosto rikkinäinen", you can always check it with the google: "tiedosto rikkinäinen site:translationproject.org" And the only link is == http://translationproject.org/PO-files/fi/gprof-2.20.1.fi.po == There you can find the text: {{{ #: gmon_io.c:370 #, c-format msgid "%s: %s: found bad tag %d (file corrupted?)\n" msgstr "%s: %s: virheellinen tunniste %d löytyi (tiedosto rikkinäinen?)\n" }}} Here you will see that the localized text means "file corrupted" and it can be found in gmon_io.c file on the line 370. The problem with the Haiku localization is that you have not selected .po file form for catkeys and origin of localized texts is not so easy to trace. If we will localize also command line tools, so we are making use of Haiku easier for millions of future users, but a bit difficult for some hundred developers. Most users probably never use the command line tools, but I know that if some accidentally do so, they can became very confused and angry: "What is that application doing? What does it do with my computer?" That is because they do not understand English output. -- Ticket URL: <http://dev.haiku-os.org/ticket/6318#comment:7> Haiku <http://dev.haiku-os.org> Haiku - the operating system.