Hi.
I'm compiling libreoffice 6 on ubuntu for checking my new (korean)
translation.
However, it takes forever--it's running for 6 hours so far.
Q1. Is there a way to compile a language pack only?
I use ubuntu 16.04, x64
Q2. How to compile language pack with files from pootle, not from gerrit?
wh
Hi.
I'm a Japanese translation volunteer, remember that I'm not a
programmer, not a engineer.
If you have built LibreOffice from the source and your purpose is
checking your translation, I can show you my way:
1. Download .po files which you want check from Pootle.
2. remove comments from the
Hi, Kiyotaka Nishibori
I followed your instructions.
It works well. Now I can check my translations in few mins.
Thank you very much.
FYI, my process was
*1. Download Libreoffice source*
$ git clone git://anongit.freedesktop.org/libreoffice/core libreoffice
$ cd libreoffice
*2. Build libreoff
On 16.03.2018 09:07, Jihui Choi wrote:
Hi, Kiyotaka Nishibori
I followed your instructions.
It works well. Now I can check my translations in few mins.
Thank you very much.
FYI, my process was
*1. Download Libreoffice source*
$ git clone git://anongit.freedesktop.org/libreoffice/core libreo
On 20.03.2018 07:54, Krunose wrote:
On 16.03.2018 09:07, Jihui Choi wrote:
Hi, Kiyotaka Nishibori
I followed your instructions.
It works well. Now I can check my translations in few mins.
Thank you very much.
FYI, my process was
*1. Download Libreoffice source*
$ git clone git://anongit.fr
On 20.03.2018 10:24, Heiko Tietze wrote:
On 20.03.2018 07:56, Krunose wrote:
On 20.03.2018 07:54, Krunose wrote:
On 16.03.2018 09:07, Jihui Choi wrote:
Hi, Kiyotaka Nishibori
I followed your instructions.
It works well. Now I can check my translations in few mins.
...
Think that shouldn't
Hi, Kruno.
Please add this as well.
For local Help pack,
in step 2,
$ ./autogen.sh --with-help --with-lang="ko"
in step 3,
(for Help)
$ \cp -fR ko/libo_help/*
libreoffice/translations/source/ko/helpcontent2/source/text/
$ \mv
libreoffice/translations/source/ko/helpcontent2/source/text/auxiliary
On 21.03.2018 17:21, Jihui Choi wrote:
Hi, Kruno.
Please add this as well.
For local Help pack,
in step 2,
$ ./autogen.sh --with-help --with-lang="ko"
in step 3,
(for Help)
$ \cp -fR ko/libo_help/*
libreoffice/translations/source/ko/helpcontent2/source/text/
$ \mv
libreoffice/translations/s
Hi,
is there a way to use the already built version (like a master daily build)
and just build the lang-pack without the need of pulling and building the
whole package?
Also, the instructions are not clear about messages.po file names. Current
po file have some name messages.po and others not (li
On 22.03.2018 09:44, Martin Srebotnjak wrote:
Hi,
is there a way to use the already built version (like a master daily build)
and just build the lang-pack without the need of pulling and building the
whole package?
What do you mean by whole package? I don't think language pack is
available in
Hi Martin.
On Thu, Mar 22, 2018 at 5:44 PM, Martin Srebotnjak wrote:
>
> Also, the instructions are not clear about messages.po file names. Current
> po file have some name messages.po and others not (like the files in the
> dictionaries folder or the officecfg folder). So are you referring to
>
On 23.03.2018 17:22, Jihui Choi wrote:
Hi Martin.
On Thu, Mar 22, 2018 at 5:44 PM, Martin Srebotnjak wrote:
Also, the instructions are not clear about messages.po file names. Current
po file have some name messages.po and others not (like the files in the
dictionaries folder or the officecfg f
On 23.03.2018 23:27, Jihui Choi wrote:
To Krunose
That means that when I extract .po files to 'translations' folder in source
tree, I need to check if .po files in individual directory is named
'messages.po' or differently.
If name is 'messages.po' then command
msgfmt -o instdir/program/
On 24.03.2018 07:03, Krunose wrote:
On 23.03.2018 23:27, Jihui Choi wrote:
To Krunose
That means that when I extract .po files to 'translations' folder in
source
tree, I need to check if .po files in individual directory is named
'messages.po' or differently.
If name is 'messages.po' then co
Hi,
I'm sorry I'm late.
I found some new facts about "make build-l10n-only":
1. The command generates a .mo file in workdir/MoTarget if it does not
exist here or is older than .po file for the .mo file. The .mo file
name is ".mo". means final .mo name like 'sc',
'dkt' and so on; for exsample,
On 25.03.2018 15:19, Kiyotaka Nishibori wrote:
Hi,
I'm sorry I'm late.
I found some new facts about "make build-l10n-only":
1. The command generates a .mo file in workdir/MoTarget if it does not
exist here or is older than .po file for the .mo file. The .mo file
name is ".mo". means final .mo
Sorry, everyone,
I am very confused. I looked into macOS lang-pack and saw what this
required mo building and renaming process produces.
Can someone explain where some existing po files finish after this process
(I am listing them below) - because they contain like 7000 UI strings that
- where do
17 matches
Mail list logo