Are those message files compiled with gencat(1)? Some platforms have a command that does the reverse, e.g. converts a compiled message catalog file back into the source form (or an alternative form for human consumption that can't be fed back into gencat - my human-readable output may be different from other platforms, as I had no example at the time to compare with). Solaris didn't, so I wrote one from scratch some years ago - I guess I wanted to add a message to an existing catalog. The command (both mine and on the platforms that already have it) is called "dspcat". On Solaris, mine will work better because there's no interface for enumerating messages, but I take advantage of the internal structure of the message files. On other OS's, it will still work, but with brute force (trying all possible message set and message numbers), so it'd definitely be slower, although unless a message file was quite large, one might not notice. I just fixed a minor thing in it (missing include file) after trying it on my Mac (where I only found one actual .cat file, as opposed to something of that name), and the brute force used there wasn't slow enough to be bothered by.
Are there situations where that would be helpful? If so, it's available at http://www.smart.net/~rlhamil/goodies/dspcat.tar.gz I think I even included a man page. :-) > On Jun 27, 2018, at 16:29, Edmond Orignac <edmond.orig...@wanadoo.fr> wrote: > > On the question of localizing, I have written some notes at: > > http://edmond.orignac.pagesperso-orange.fr/localisation.en.html > > By experimenting with an Occitan locale and a Latin locale on linux, I can > say that what matters is whether an underlying linux locale is already > present. In the case of Occitan it was the case, and simply translating the > messages and placing the *.cat file in /usr/dt/lib/nls/msg/oc_FR.ISO8859-1/ > directory and adding the line > > export LANG=oc_FR.ISO8859-1 > > to .dtprofile was all that was needed to have window titles and menus in > Occitan. I would expect that simply applying iconv or GNU recode to the > es_ES.ISO8859-1 and compiling the resulting *.msg files with gencat would > work. For generating the app-defaults, the backdrops/palettes description, > you have to apply a program merge that is in the CDE source tree. For merge > to work correctly, you need to indicate a UTF8 locale with merge -lang > es_ES.UTF8 <file.nls file.tmsg > desc.es_ES.UTF8. > > With Latin, there was no locale on Linux, and things were more complicated. > In the archive: > > http://edmond.orignac.pagesperso-orange.fr/la_FR.ISO8859-1.tgz > > the file Installation explains the steps for installation. You need first to > install a locale for linux, then make X aware of the existence of the new > locale. After that, you can install the message catalogues > app-defaults etc... > > There are a few shell scripts that I have used to generate the locales > appdefgen.sh catgen.sh typegen.sh configen.sh in the different directories > that can be adapted for creating the files in es_ES.UTF8. > > I'll try to create an fr_FR.UTF8 locale for CDE along the lines I have > sketched. Since the linux locale is already on my computer, this should be > simple unless either gencat of merge is unable to handle UTF8. > > > > Le 26/06/2018 à 20:33, Jon Trulson a écrit : >> Antonis Tsolomitis did this for the Greek UTF8 locale. Unfortunately, we >> didn't have the foresight to document all of the steps required. >> >> This would make a great wiki article, if you can figure it out. It would >> help others in the future who want to do translations. >> >> Maybe Antonis can describe the details, if he remembers :) But it can be >> done. In your case it might even be easier in some ways, as we already have >> a es_ES.ISO8859-1 locale, whereas Antonis had to do the translations >> directly as we had no support for any Greek locales. >> >> Some experimenting shows that 'iconv' can be used to translate between >> es_ES.ISO8859-1 and a es_ES.UTF-8 message catalog easily. I just don't know >> if that's enough, or what other steps might be involved. >> >> I know most of the work would probably be in programs/localized/, with some >> components having their own localization (mainly in the form of message >> catalogs). >> >> -jon >> >> On 06/24/2018 11:06 AM, José Carlos Carrión Plaza wrote: >>> Hi co-listers: >>> >>> I'm willing to begin CDE es_ES.UTF-8 localizing. >>> >>> Are they a subproject like this? >>> >>> Anyone working in this? >>> >>> Any roadmap of such type of work? >>> >>> Any ideas? >>> >>> Thanks in advance. >>> >> > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > cdesktopenv-devel mailing list > cdesktopenv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel >
signature.asc
Description: Message signed with OpenPGP
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
