Re: [xz-devel] Go/Golang bindings for xz
Hello! On 2021-04-12 James Fennell wrote: > Over the last couple of weeks I've been working on a project to add > Go bindings for the xz format: https://github.com/jamespfennell/xz :-) > The project uses the Go technology cgo to compile the relevant > liblzma C files automatically and link them in with the Go binary. That made me wonder about config.h and the #defines. With a really quick look I found https://github.com/jamespfennell/xz/blob/main/lzma/lzma.go which sets a few #defines but it's quite limited, for example, a comment tells that only 64-bit systems are supported. I also don't see TUKLIB_FAST_UNALIGNED_ACCESS which is good on 32/64-bit x86 and some ARMs to get a little better encoder performance. Also #define TUKLIB_SYMBOL_PREFIX lzma_ could be good to have to ensure that all symbols begin with "lzma_". Of course these don't matter if the system liblzma is used instead. I understood that it's an option too. > Lasse, would you be interested in adding a link under the bindings > section of the xz website? I can. Since there are other bindings to use liblzma, I wonder if some of those should be listed too. What do you think? I have no Go experience so I have no idea which are good or already popular. Thanks! -- Lasse Collin | IRC: Larhzu @ IRCnet & Freenode
Re: [xz-devel] Status of man page translations?
On 2021-04-15 Mario Blättermann wrote: > Am So., 11. Apr. 2021 um 20:48 Uhr schrieb Lasse Collin > : > > I suppose I can just submit a snapshot from the master branch. I have done this. > I am curious to see when the first new translations will arrive :) Me too. It's a lot of work to translate them all. -- Lasse Collin | IRC: Larhzu @ IRCnet & Freenode
Re: [xz-devel] Status of man page translations?
Hello Lasse, Am So., 11. Apr. 2021 um 20:48 Uhr schrieb Lasse Collin : > > On 2021-04-04 Mario Blättermann wrote: > > But what ist the blocker which still prevents you from creating an > > intermediate tarball, send it to the TP coordinator and tell him to > > create a new domain named "xz-man"? > > I suppose I had forgotten it. If there were other reasons, I have > forgotten them too. Sorry. > > I suppose I can just submit a snapshot from the master branch. > xz-man.pot is compatible with v5.2 for now. xz.pot isn't compatible > between the branches though but if 5.2.6 is needed (impossible to know > now) maybe it's not that bad: > > The command line tool translations in v5.2 have strings that are > difficult to get right. The master branch has such strings too but not > as many. For the 5.2.5 release, many translations didn't pass basic > quality control due to these strings. Some translators (individuals or > teams) replied to my emails about suggested white-space corrections, > some didn't. Thus multiple translations were omitted from 5.2.5. With > this background I feel that if 5.2.6 is needed I won't consider any > *new* xz.po files for it anyway; new xz-man.po languages would be fine. > OK, good idea. I am curious to see when the first new translations will arrive :) Best Regards, Mario
