Hi!
I am mainly interrested in coding, I realy enjoy it!
But I thought that I perhaps could be of help on translation as well.
I am so sorry I missed to continue with build as well.
So I have tried and run into problems again.
I tried:
apt-get build-dep libreoffice
and got message back:
Can not find any source code for libreoffice.
So I tried:
apt-get build-dep openoffice.org
and got message back:
Building dependencies for openoffice.org could not be satisfied.
(directly translated from swedish)
So I tried:
./autogen.sh
and got message back:
error: Could not find CUPS. Install libcupsys2-dev or cups???-devel.
So I tried:
apt-get install libcupsys2-dev
and got message back:
Dependency problem, Depending on: libcups2-dev but it will not be
installed.
So I tried:
apt-get install libcups2-dev
and got message back:
Depending on: libcups2(1.3.8-1+lenny9) but 1.3.10-1 will be installed
I am using Debian 2.6.26-2-amd64.
I hope I do not destroy mailing-list to much.
Sorry if I am!
Thanks!
Marcux
ons 2011-07-06 klockan 18:53 +0700 skrev Korrawit Pruegsanusak:
Hello Marcus,
On 05/07/2011 21:13, Marcus Pedersén wrote:
I have written code in C++ and I realy like that language.
I am interested in coding and as I am from sweden I would be able to
help out with translation into swedish.
If you want to do some translations *only*, you don't need to build libo.
Instead go to https://translations.documentfoundation.org/ or
http://wiki.documentfoundation.org/Language for more info.
Best Regards,
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.