KeyID builds

l10n
#1

Hi,

I created KeyID builds (see
http://wiki.services.openoffice.org/wiki/KeyID_Build for explanation).

These builds are based on LibreOffice 3.4 beta 2 en-US. Three install
sets are available: Windows, Linux/x86 DEB, Linux/x86 RPM.

http://ftp.fsf.hu/LibreOffice/KeyID/

Let me know, if you have any questions.

Best regards,
Andras

#2

Questions may come later, but first, thanks a lot, it's really great :slight_smile:
Kind regards
Sophie

#3

Nice work! It's going to be very useful!

Thanks!

Pau

#4

Thank you!

I might add that these builds finally do NOT have the major bug (https://bugs.freedesktop.org/show_bug.cgi?id=35879, being unable to save or export) which manifested itself on my system, before. Now I'll be able to actually try LibreOffice. Let's hope the change won't get reverted. :slight_smile:

-Yury

I created KeyID builds (see

...

These builds are based on LibreOffice 3.4 beta 2 en-US. Three install

...

#5

I confirm too. This build can save and export.

But, I can't understando de keys. They appears as hexadecimal non
decimal. Is different from
http://wiki.services.openoffice.org/wiki/KeyID_Build. Now it's hard
Also, which is the howto for find a string with these string keyids ?
Really would be very usefull for translators!

(See attached image)

#6

Wiki has an old screenshot. I don't like these Key IDs either... Hard
to read them. This is what OOo uses now. I can change them later.

How to use:
You want to find for example the File menu in the source. You see that
key ID is 5wl7ot.
Search for 5wl7ot in KeyID.sdf. E.g.:
$ grep 5wl7ot KeyID.sdf
Now you see where this string is coming from:
officecfg registry\data\org\openoffice\Office\UI\GenericCommands.xcu
So it is in officecfg\registry\data\org\openoffice\Office\UI.po.

Best regards,
Andras

#7

Ahá, Ok Andras,
I was thinking in Pootle.

#8

Well, ideally translate-toolkit / Pootle could put key ID in comment,
so we could search for them in Pootle. Key IDs are generated with a
deterministic algorithm, so it would be possible. Maybe for
LibreOffice 3.5. :slight_smile:

Best regards,
Andras

#9

translate-toolkit already does something similar with podebug - I think it might even output the same form.

These numbers could go in comments, probably an easy hack, or better into the actual search functionality in Pootle in which case the PO files wouldn't need to be anything more special then what we currently have.

Anyone wanting to give this a go to hack?

#10

Hello Andras

Are you going to generate the keyID's strings for LO 3.5?

Also, I thougt KeyID was like another language... If that is the case, then is it possible for me to make a build myself with the KeyID?. If so, what
is the language code I must append to autogen.sh

--with-lang=pt-BR en-US<???>

Thank you

Olivier

#11

Hello Olivier,

Hello Andras

Are you going to generate the keyID's strings for LO 3.5?

Also, I thougt KeyID was like another language... If that is the case, then
is it possible for me to make a build myself with the KeyID?. If so, what
is the language code I must append to autogen.sh

--with-lang=pt-BR en-US<???>

KeyID generation is part of the non-release build. So I expect that
betas will have them. For yourself you can configure it with the 'qtz'
language code.

Best regards,
Andras

#12

Hi Andras, *,

Hello Olivier,

> Hello Andras
>
> Are you going to generate the keyID's strings for LO 3.5?
>
> Also, I thougt KeyID was like another language... If that is the case,
then
> is it possible for me to make a build myself with the KeyID?. If so, what
> is the language code I must append to autogen.sh
>
> --with-lang=pt-BR en-US<???>
>

KeyID generation is part of the non-release build. So I expect that
betas will have them. For yourself you can configure it with the 'qtz'
language code.

There are no qtz packages for 3.5 beta 0 on
http://dev-builds.libreoffice.org/pre-releases/deb/x86/
Or has it another code there?

Regards,
Mihkel

#13

Hi Mihkel,

There are no qtz packages for 3.5 beta 0 on
http://dev-builds.libreoffice.org/pre-releases/deb/x86/
Or has it another code there?

There seems to be a little confusion regarding the KeyID build. I hope
we can have it for the next beta.

Best regards,
Andras