Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index 

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 "<DOMAIND><LANG>.mo". <DOMAIN> means final .mo name like 'sc', 'dkt' and so on; for exsample, if <DOMAIN> is 'sc' and <LANG> is 'ja', "make build-l10n-only" generates 'scja.mo' in the directory. 

2. Timestamp of a <DOMAIN><LANG>.mo is when the .mo file is generated.
3. THe command copies a workdir/MoTarget/<DOMAIN><LANG>.mo as instdir/program/resource/<LANG>/LC_MESSAGES/<DOMAIN>.mo if the <DOMAIN>.mo does not exist or is older than the <DOMAIN><LANG>.mo.
These things mean that if we remove .mo files from workdir/MoTarget before running "make build-l10n-only", we can get updated .mo file by the command. Could you please reproduce it?
Ofcourse, direct generation of .mo files to instdir/... is also available. 
--
Regards,

Kiyotaka

P.S. to Kruno
Thank you for your writeing the article in wiki and I'm sorry, we may need to rewrite it.
2018 3月 25日 (日), 4:48 午前 に Krunose <kruno.se@gmx.com> が書いたメッセージ: 
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 command
msgfmt -o instdir/program/resource/<langCode>/LC_MESSAGES/<mofile> 
<dir>/messages.po
needs to be run in that particular directory on right side of the table in Wiki page by replacing '<mofile>' in command with information from left side 
of the table on Wiki page?
Basically "Yes", but you don't have to check every directories nor po files 
because step 3, 5 will do it for you. Of course you have to make a
script for step 5 though.


After dealing with renaming, command

     make build-l10n-only

needs to be run?
Yes. step 4 makes some mo files from po files on step 3, which is not 
named as messages.po.
But it doesn't care about messages.po files. So we need step 5.
If I'm right, then all what's needed is to switch places of fourth and fifth 
step (and simplify instructions).
I'm not sure about this. The original instruction came from Kiyotaka. 
However I guess you're right. It could be switched.
For me, current instructions is good. Because step 3, 4 are dealing
with not 'messages.po' files
and step 5 is about 'messages.po' files.
And you need to add step 6 from my instruction at the end of section on wiki. 
"sudo make install"

Those instructions(both of Kiyotaka's and mine) are about building
libreoffice from the source.
I tried just copying .mo files to already installed Libreoffice via
apt, but it didn't work.

Here is my post about this.
http://libreoffice.tistory.com/entry/%EB%A6%AC%EB%B8%8C%EB%A0%88%EC%98%A4%ED%94%BC%EC%8A%A4-%EB%8F%84%EC%9B%80%EB%A7%90-%ED%8C%A8%ED%82%A4%EC%A7%80-%EB%B9%8C%EB%93%9C%ED%95%98%EA%B8%B0-%EC%9A%B0%EB%B6%84%ED%88%AC-1604  

Thanks, I'll update later today.
Seams that problem is not with instructions as with lack of our understanding of the process and directory structure. I'll test and update instructions. 

Thanks,

Kruno



Hi,

I've done my best

https://wiki.documentfoundation.org/Development/BuildingOnLinux#Building_translated_user_interface_with_.po_files_from_Pootle

hope at least somebody will find this helpful.

Kruno











--
Regards,
Jihui Choi


On Sat, Mar 24, 2018 at 7:02 AM, Krunose <kruno.se@gmx.com> wrote:

On 23.03.2018 17:22, Jihui Choi wrote:

Hi Martin.
On Thu, Mar 22, 2018 at 5:44 PM, Martin Srebotnjak <miles@filmsi.net> 
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 pre-6.0 po files (no renaming needed, use step 4) and post-5.4 po-files 
(use step 5)?

on Pootle
1) some files has the names as messages.po
2) some others has different names.

It has to be treated differently.(I don't know why though)
So..

step 3 is for 1) case
step 5 is for 2) case
I'm not an expert but it works for me(thanks to Kiyotaka). Good luck.
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/resource/<langCode>/LC_MESSAGES/<mofile> 
<dir>/messages.po
needs to be run in that particular directory on right side of the table in Wiki page by replacing '<mofile>' in command with information from left side 
of the table on Wiki page?

After dealing with renaming, command

     make build-l10n-only

needs to be run?
If I'm right, then all what's needed is to switch places of fourth and fifth 
step (and simplify instructions).

Can you, please, confirm this?



Thanks,

Kruno
||


--
Regards,
Jihui Choi
On Thu, Mar 22, 2018 at 5:44 PM, Martin Srebotnjak <miles@filmsi.net> 
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?
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 pre-6.0 po files (no renaming needed, use step 4) and post-5.4 po-files 
(use step 5)?
Also, could you publish a rename/move script for all ui and help po files 
of the current 6.0 and master tree?

Thanks, m.

2018-03-21 23:07 GMT+01:00 Krunose <kruno.se@gmx.com>:


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/sourc
e/ko/helpcontent2/source/text/
$ \mv
libreoffice/translations/source/ko/helpcontent2/source/text/auxiliary.po  
libreoffice/translations/source/ko/helpcontent2/source/

Thanks.



Hi,

I finally added everything to
https://wiki.documentfoundation.org/Development/BuildingOnLinux#Building_  
translated_user_interface_with_.po_files_from_Pootle

could Kiyotaka and you check everything. I'll edit if needed.

Thanks,
Kruno





--
Regards,
Jihui Choi
On Tue, Mar 20, 2018 at 6:37 PM, Krunose <kruno.se@gmx.com <mailto: 
kruno.se@gmx.com>> wrote:



      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 that be added to

              Wanted to say 'Shouldn't that be added to [...]'

          You are welcome to edit the page. :-)


      Will do later today.

      Kruno
-- To unsubscribe e-mail to: l10n+unsubscribe@global.libreo 
ffice.org
<mailto:l10n%2Bunsubscribe@global.libreoffice.org>
      Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-un
subscribe/
<https://www.libreoffice.org/get-help/mailing-lists/how-to-u
nsubscribe/>
      Posting guidelines + more:
      https://wiki.documentfoundation.org/Netiquette
<https://wiki.documentfoundation.org/Netiquette>
List archive: https://listarchives.libreoffice.org/global/l10n/ 
<https://listarchives.libreoffice.org/global/l10n/>
All messages sent to this list will be publicly archived and 
      cannot be deleted




--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-un 
subscribe/
Posting guidelines + more:
https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be 
deleted


--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/  Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette 
List archive: https://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be 
deleted



--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette 
List archive: https://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be 
deleted






--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette 
List archive: https://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted 


--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Context

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.