Re: [libreoffice-l10n] Untranslated extensions

2010-12-16 Thread Olivier Hallot

Hi Rimas

pt-BR, please.

Thank's for you wonderful work.

Regards
Olivier

Em 14-12-2010 19:21, Rimas Kudelis escreveu:

2010.12.14 22:12, Andras Timar rašė:

2010.12.14. 20:23 keltezéssel, Martin Srebotnjak írta:

2010/12/14 Andras Timartima...@gmail.com


As a temporary solution, can't we just translate the .properties files
and bundle the translated .properties? All you need to do is to update
tarball at the end of the process.


Andras,

send us the .properties files (or a link thereof), please!

Thanks,
m.


Hi Martin,

http://cgit.freedesktop.org/~kohei/nlpsolver/tree/src/locale/NLPSolverCommon_en_US.properties


and

http://cgit.freedesktop.org/~kohei/nlpsolver/tree/src/locale/NLPSolverStatusDialog_en_US.properties


Question to all localizers: how many of you want to translate this?
Please note that this is highly technical - e.g. I'm not sure I want
this in Hungarian. I can convert .properties to .po and I can ask Rimas
to put them into Pootle, but I need to know, if it worths the effort. It
is already translated to German.


No need to convert actually, Pootle supports .properties files natively.
I've just slightly altered the names of all four (2 English and 2
German) files, and they're good to go:
http://translations.documentfoundation.org/projects/extensions/.

Those who want to translate using Pootle should just ask to enable
translating this project into their language, and that's about it.

Rimas




--
Olivier Hallot
Founder, Steering Commitee Member - The Document Foundation
Translation Leader for Brazilian Portuguese

--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [libreoffice-l10n] Untranslated extensions

2010-12-16 Thread Rimas Kudelis

2010.12.16 12:47, Olivier Hallot rašė:

Hi Rimas

pt-BR, please.

Thank's for you wonderful work.


Done. You're welcome! :)

Rimas


--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [libreoffice-l10n] Untranslated extensions

2010-12-16 Thread Rimas Kudelis

2010.12.16 13:44, Jesús Corrius rašė:

Labas Rimas,

Prašome ca-ES.

Labai ačiū!


Done :) Prašom!

Rimas


--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


[libreoffice-l10n] About occitan-lengadocian's translations

2010-12-16 Thread bruno gallart

Occitan-lengadocian's project


Hi all and I think more for Rimas,

For informations, I have finished the occitan-lengadocian's translations 
on pottle.


Cheers,
Bruno






--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [libreoffice-l10n] About occitan-lengadocian's translations

2010-12-16 Thread Rimas Kudelis

Hi Bruno,

2010.12.16 14:47, bruno gallart rašė:
For informations, I have finished the occitan-lengadocian's 
translations on pottle.


Please avoid starting new topics in the old thread by just pressing 
reply on a random message in future.


Do you want to also translate the solver extension?

Rimas


--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


[libreoffice-l10n] Re: Embedded parts and wikihelp/HC2

2010-12-16 Thread Jan Holesovsky
Hi Sophie,

On 2010-12-16 at 07:38 +0300, Sophie Gautier wrote:

 I've two questions concerning the wikihelp/HC2, there is no emergency 
 for the answer, I know you're busy, but I don't want to forget to ask ;)

We are all busy, I am sure; thank you for the explicit CC:, it is then
much easier to give this the priority it deserves! :-)

First of all - thank you all for the input on the wikihelp.  This is
software, so any [or at least many ;-)] changes are of course possible.
So far, it seems to me that what Martin proposed fits all the [in
alphabetical order] developers, documentation team, and l10n; I mean:

- 8 -
I propose you develop a system to have English help editable on wiki but
fully transportable back to the po/xliff system (interchangeable).
All the translations would start from the English po/xliff help files
and decide whether to
a) strictly translate English help (like we Slovenians decided) and keep
working with po/xliff files; the online help would be updated from these
files at least with every minor and major release;
or
b) develop their own help in the wiki and never go back again;
- 8 -

To summarize that, the best seems to be that:

- only the English pages will be editable
  - like eg. http://help.libreoffice.org/Common/Save_As
  - but the lang versions, like
http://help.libreoffice.org/Common/Save_As/cs
will be _not_ editable

- strings from the English pages will be uploaded to pootle
  - so that you can work the way you are used to

- existing translations will be converted
  - so that the work is not lost, ie. everything that has been
translated so far has to be translated in the wikihelp version too

- the pootle tranlations will be applied over the English version
  - but if a language team decides that they want to translate directly
in the wikihelp, their language version will be open for editing
directly in the wikihelp

How does that sound?  If this plan is acceptable for all, I can go
ahead, and start working on this :-)

Only one problem I can think of is the time; I am not sure if I can get
that 100% before the final release, so - it might happen that the
wikihelp will be English only at the time of 3.3 final, but filed with
the translated versions as soon as the above works (but it is an online
thing, so the deployment can be independent of the release date, there
is still room for improvements).  We will have the translated helppacks,
so hopefully it is not an issue. 

 Currently in the HC2 files, pages are composed by a mix of embedded 
 chunks and local strings. We use two files to get the KID of the string, 
 to display the embedded chunks, the .xhp tree and the OS dependent parts 
 in order to do l10n QA on the files.
 
 I've added a screen shot of the result to my page on the wiki [1].
 
 How somebody contributing to the wikihelp will see these embedded parts 
 or OS specific parts. How will he knows that it should not make it to 
 much particular to a certain page because it will appear elsewhere on 
 other pages in the HC2?

This is a very good question.  In the current implementation, I do not
treat embedding in a special way, and just copy the text there directly.

The following is the page you have shown on the screenshot:
 
http://help.libreoffice.org/Writer/Shortcut_Keys_for_Writer 

Ie. the 'Some shortcut ...' text is directly there, not an embedded
string.

If we want to address this, it is of course solvable too; the only
problem might be that for everything that is supposed to be embedded, it
has to have a special page, like Embed:Some_id, an in the text, it would
be used like {{Embed:Some_id}}.

For example, a text like:

file swriter/file1.xhp:
  paragraph ...variable ...somethingSomething to
embed/variable/paragraph

file swriter/file2.xhp:
  embed href=...file.xhp#something

would in the wiki look like:

Page Embed:file1_something
  Something to embed

Page Writer/file1
  {{Embed:file1_something}}

Page Writer/file2
  {{Embed:file1_something}}

Documentation team - is that acceptable for you?

OS specific parts are already solved differently, there is a template
{{System}}, used like {{System|mac=Mac string|win=Windows string|
default=something default}}.

The template page itself does not work yet (ie. always the default
choice is shown), but I'll fix that ASAP.

 Some pages are mostly composed by embedded chunks, if those embedded 
 part are removed, would that mean we will have to duplicate the 
 localization?

Yes, they would have to be duplicated, if the {{Embed:...}} solution
outlined above is not acceptable (though I hope it is).

Regards,
Kendy


-- 
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


[libreoffice-l10n] Re: [Libreoffice] Embedded parts and wikihelp/HC2

2010-12-16 Thread Kohei Yoshida
On Thu, 2010-12-16 at 14:44 +0100, Jan Holesovsky wrote:
 - the pootle tranlations will be applied over the English version
   - but if a language team decides that they want to translate
 directly in the wikihelp, their language version will be open for
 editing directly in the wikihelp 

To me this part is very important.  Direct translation from English does
not always sound right in some languages.  So, I appreciate having this
possibility in the new wikihelp.

Kohei

-- 
Kohei Yoshida, LibreOffice hacker, Calc
kyosh...@novell.com


-- 
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


[libreoffice-l10n] Features list

2010-12-16 Thread Sophie Gautier

Hi all,
[sorry for the cross post, but I need you all on this]

I've finished to complete the feature list [1] on the wiki that Marc did 
upload some time ago (Cor you get the same but not complete and not sorted).


So, dear developers if you preferred feature is not there, add it to the 
page or shout at me ;)


Dear QA members, please also, use this list against RC2 to test these 
new or enhanced functionalities. We will have more formal TCS next time, 
but, we need your help to make sure every thing is ok and there is no 
regression.


Dear marketing people, I'm sure Italo will give you some guidance on the 
most important ones at the marketing level, but may be you can make also 
some proposal and design a page so that he only has to review it.


Dear localizer, I hope this will help you to test/check your 
translation. If you need more details or don't find a functionality, 
don't hesitate to ask on the list.


And finally, dear documentation team, I'm sure we will soon have good 
knowledge on how to use those new and unavoidable features our 
developers have designed with the help of your nice writings :-)


I would like to thank every body for the great work that has been 
already done and will be done for our first version all together :-)


[1] 
http://wiki.documentfoundation.org/Marketing/LibOReleaseEvents/LOPressKit/FeatureList3.3


Kind regards
Sophie
--
Founding member of The Document Foundation

--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


[libreoffice-l10n] Re: [Libreoffice] Features list

2010-12-16 Thread David Nelson
Hi Sophie, :-)

Thanks for that, I will include them on the site ASAP. ;-)

David Nelson

-- 
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***



[libreoffice-l10n] Re: Embedded parts and wikihelp/HC2

2010-12-16 Thread Sophie Gautier

Hi Kendy, all,
On 16/12/2010 16:44, Jan Holesovsky wrote:

Hi Sophie,

On 2010-12-16 at 07:38 +0300, Sophie Gautier wrote:


I've two questions concerning the wikihelp/HC2, there is no emergency
for the answer, I know you're busy, but I don't want to forget to ask ;)


We are all busy, I am sure; thank you for the explicit CC:, it is then
much easier to give this the priority it deserves! :-)


Thank you :)


First of all - thank you all for the input on the wikihelp.


you're welcome, it's an important work for all of us.
 This is

software, so any [or at least many ;-)] changes are of course possible.
So far, it seems to me that what Martin proposed fits all the [in
alphabetical order] developers, documentation team, and l10n; I mean:

- 8  -
I propose you develop a system to have English help editable on wiki but
fully transportable back to the po/xliff system (interchangeable).
All the translations would start from the English po/xliff help files
and decide whether to
a) strictly translate English help (like we Slovenians decided) and keep
working with po/xliff files; the online help would be updated from these
files at least with every minor and major release;
or
b) develop their own help in the wiki and never go back again;
- 8  -

To summarize that, the best seems to be that:

- only the English pages will be editable
   - like eg. http://help.libreoffice.org/Common/Save_As
   - but the lang versions, like
 http://help.libreoffice.org/Common/Save_As/cs
 will be _not_ editable


ok


- strings from the English pages will be uploaded to pootle
   - so that you can work the way you are used to


ok


- existing translations will be converted
   - so that the work is not lost, ie. everything that has been
 translated so far has to be translated in the wikihelp version too


ok


- the pootle tranlations will be applied over the English version
   - but if a language team decides that they want to translate directly
 in the wikihelp, their language version will be open for editing
 directly in the wikihelp


ok, and I agree with Kohei, this second step is also very important.


How does that sound?  If this plan is acceptable for all, I can go
ahead, and start working on this :-)


For me it is, and I think that every body will the happy with your 
proposal. Thanks a lot :-)


Only one problem I can think of is the time; I am not sure if I can get
that 100% before the final release, so - it might happen that the
wikihelp will be English only at the time of 3.3 final, but filed with
the translated versions as soon as the above works (but it is an online
thing, so the deployment can be independent of the release date, there
is still room for improvements).  We will have the translated helppacks,
so hopefully it is not an issue.


Yes, it's not an issue, we can take time to test with the l10n team and 
improve every thing when it's needed. And you don't have to spend your 
nights on this too ;)
Also, I think our marketing guys will be happy to make some buzz around 
this important feature when it will be ready and it may be even better 
if it's not at the same time of 3.3, what do you think?



Currently in the HC2 files, pages are composed by a mix of embedded
chunks and local strings. We use two files to get the KID of the string,
to display the embedded chunks, the .xhp tree and the OS dependent parts
in order to do l10n QA on the files.

I've added a screen shot of the result to my page on the wiki [1].

How somebody contributing to the wikihelp will see these embedded parts
or OS specific parts. How will he knows that it should not make it to
much particular to a certain page because it will appear elsewhere on
other pages in the HC2?


This is a very good question.  In the current implementation, I do not
treat embedding in a special way, and just copy the text there directly.

The following is the page you have shown on the screenshot:

http://help.libreoffice.org/Writer/Shortcut_Keys_for_Writer

Ie. the 'Some shortcut ...' text is directly there, not an embedded
string.

Yes, that's what I've seen.


If we want to address this, it is of course solvable too; the only
problem might be that for everything that is supposed to be embedded, it
has to have a special page, like Embed:Some_id, an in the text, it would
be used like {{Embed:Some_id}}.

For example, a text like:

file swriter/file1.xhp:
   paragraph ...variable ...somethingSomething to
embed/variable/paragraph

file swriter/file2.xhp:
   embed href=...file.xhp#something

would in the wiki look like:

Page Embed:file1_something
   Something to embed

Page Writer/file1
   {{Embed:file1_something}}

Page Writer/file2
   {{Embed:file1_something}}


ok, I understand.


Documentation team - is that acceptable for you?

OS specific parts are already solved differently, there is a template
{{System}}, used like {{System|mac=Mac string|win=Windows string|
default=something default}}.

The template page itself does 

[libreoffice-l10n] To make the (Vietnamese) translation to be taken from pootle

2010-12-16 Thread Nguyen Vu Hung
Hi all,

I want to make Vietname translation should be taken from Pootle.
Who is the person should I contact?

http://wiki.documentfoundation.org/Translation_for_3_3#Translation_matrix_of_LibreOffice_3.3_lo-build-.2A.po_files.

-- 
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remo...@gmail.dot.com , YIM: vuhung16 , Skype: vuhung16plus
A brief profile: http://www.hn.is.uec.ac.jp/~vuhung/Nguyen.Vu.Hung.html

-- 
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [libreoffice-l10n] To make the (Vietnamese) translation to be taken from pootle

2010-12-16 Thread Sophie Gautier

Hi Hung,
On 16/12/2010 18:45, Nguyen Vu Hung wrote:

Hi all,

I want to make Vietname translation should be taken from Pootle.
Who is the person should I contact?

http://wiki.documentfoundation.org/Translation_for_3_3#Translation_matrix_of_LibreOffice_3.3_lo-build-.2A.po_files.

Nice to see you here :) Rimas will give you the rights on Pootle. Did 
you already subscribe?


Kind regards
Sophie

--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [libreoffice-l10n] To make the (Vietnamese) translation to be taken from pootle

2010-12-16 Thread Rimas Kudelis

Hi,

2010.12.16 17:45, Nguyen Vu Hung rašė:

I want to make Vietname translation should be taken from Pootle.
Who is the person should I contact?

http://wiki.documentfoundation.org/Translation_for_3_3#Translation_matrix_of_LibreOffice_3.3_lo-build-.2A.po_files.



I see you are already registered with Pootle. You now have all the 
necessary permissions to translate to Vietnamese.


Please also list your team on 
http://wiki.documentfoundation.org/Language_Teams and tell me if you 
want to also translate the Non-Linear solver extension (that's approx. 
100 short strings).


Also, if you will be willing to add a wiki page for your team, please 
read http://wiki.documentfoundation.org/Multilingual_Wiki before doing 
that. Note that the URL's on the Language Teams page don't conform to 
the scheme suggested by the Multilingual Wiki page, but IMO they should. :)


Rimas

--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [libreoffice-l10n] To make the (Vietnamese) translation to be taken from pootle

2010-12-16 Thread Nguyen Vu Hung
On Fri, Dec 17, 2010 at 1:10 AM, Rimas Kudelis r...@akl.lt wrote:
 I see you are already registered with Pootle. You now have all the necessary
 permissions to translate to Vietnamese.
Yes, but I don't have time yet to translate.
Is there anything else that I have to do? Is that all the translation
we make on pootle
will be integrated into git?


 Please also list your team on
 http://wiki.documentfoundation.org/Language_Teams and tell me if you want to
 also translate the Non-Linear solver extension (that's approx. 100 short
 strings).
Done,


 Also, if you will be willing to add a wiki page for your team, please read
 http://wiki.documentfoundation.org/Multilingual_Wiki before doing that. Note
 that the URL's on the Language Teams page don't conform to the scheme
 suggested by the Multilingual Wiki page, but IMO they should. :)
I have read that but for now, we wil focus on WikiHelp (which is a nice idea :)

-- 
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remo...@gmail.dot.com , YIM: vuhung16 , Skype: vuhung16plus
A brief profile: http://www.hn.is.uec.ac.jp/~vuhung/Nguyen.Vu.Hung.html

-- 
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [libreoffice-l10n] Error in NLPSolver string

2010-12-16 Thread Rimas Kudelis

2010.12.16 17:44, Paolo Pozzan rašė:

Hello all,
while translating the newly uploaded NLPSolver / NLPSolverCommon_it.properties
in Pootle, I found a string that is surely misspelled: Size of Swam should be
Size of Swarm. In fact also the notes says:
NLPSolverCommon.Properties.SwarmSize


I fixed this in Pootle. Unfortunately, I also overrode all the existing 
translations of this string, for which I'm sorry.


Everyone, please translate that string again. It will not be shown as 
missing, but it's one of the first strings in that file, so should be 
able to find it easily.




I reported the issue here just to let the translator know about it, can someone
with better knowledge than me raise the problem in a more suitable place?


Perhaps Kohei Yoshida (cc'ed) could fix this upstream?

Rimas


--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


[libreoffice-l10n] Wiki and site news

2010-12-16 Thread Sophie Gautier

Hi all,

For your information, there will be a change in the structure of the 
wiki, and there will be sub-wiki on the type : XX.wiki.libreoffice.org 
where XX is the code of your language. See Florian mail here:

http://go.mail-archive.com/W48tIAtzkhyN4musXCa_REcKvis=

Also, I would like to remind you that if you want to have an area on the 
LibreOffice site, you may request it on the website list. Christian will 
open a page for you on the Silverstripe CMS on the form of 
XX.test.libreoffice.org where XX is the code of your language and .test. 
in the meantime of the launch of the site. See the Local sites tab on 
the http://www.test.libreoffice.org site for examples.
Silverstripe is very simple to handle and has very useful 
functionalities to highlight your activities and your community.
The sites will be launched sometime next week, but you can add your page 
when you want. Also you're not tied to the English presentation, you can 
make yours if you want.


Don't hesitate if you have any question.

Kind regards
Sophie
--
Founding member of The Document Foundation

--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [libreoffice-l10n] About occitan-lengadocian's translations

2010-12-16 Thread Andras Timar
2010/12/16 bruno gallart bruno.gall...@orange.fr

 Occitan-lengadocian's project


 Hi all and I think more for Rimas,

 For informations, I have finished the occitan-lengadocian's translations on
 pottle.


Hi Bruno,

I committed/pushed your translation along with other translation updates a
few minutes ago. AFAIK git is still not tagged for RC2, so I assume your
translation will be included.

Thanks,
Andras

-- 
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [libreoffice-l10n] Re: Embedded parts and wikihelp/HC2

2010-12-16 Thread Sophie Gautier

Hi Martin,
On 16/12/2010 19:40, Martin Srebotnjak wrote:

Jan,

2010/12/16 Jan Holesovsky ke...@suse.cz mailto:ke...@suse.cz


Only one problem I can think of is the time; I am not sure if I can get
that 100% before the final release, so - it might happen that the
wikihelp will be English only at the time of 3.3 final, but filed with
the translated versions as soon as the above works (but it is an online
thing, so the deployment can be independent of the release date, there
is still room for improvements).  We will have the translated helppacks,
so hopefully it is not an issue.


I think online help must be available in all languages - it is a
stopper, if it isn't. Otherwise the lang teams will not ok the release
thus only the English version will be an official and tested release,
and all the rest will be untested. Think what that means for adoption of
LO in enterprises and government sector. Not good at all. For all other
languages 3.3 seems to be a preview what a LO will look like in 3.4, and
not a full featured version, a kind of LO beta.


This is the wikihelp that will be available only in en_US, HC2 will be 
available in all language has helppacks. What we call online help is a 
bit confusing as it was the help files available with the OOo/LO 
version. Lets speak about HC2 for the local files and wikihelp for the 
files on the wiki.



This is a very good question.  In the current implementation, I do not
treat embedding in a special way, and just copy the text there directly.

The following is the page you have shown on the screenshot:

http://help.libreoffice.org/Writer/Shortcut_Keys_for_Writer

Ie. the 'Some shortcut ...' text is directly there, not an embedded
string.

If we want to address this, it is of course solvable too; the only
problem might be that for everything that is supposed to be embedded, it
has to have a special page, like Embed:Some_id, an in the text, it would
be used like {{Embed:Some_id}}.

For example, a text like:

file swriter/file1.xhp:
paragraph ...variable ...somethingSomething to
embed/variable/paragraph

file swriter/file2.xhp:
embed href=...file.xhp#something

would in the wiki look like:

Page Embed:file1_something
  Something to embed

Page Writer/file1
  {{Embed:file1_something}}

Page Writer/file2
  {{Embed:file1_something}}

Documentation team - is that acceptable for you?


The transport of (English) help from wiki back to xliff/po must get all
the keywords references, links etc. How is that handled? Will the index
in LO offline help work after such a backport from wiki? This is of
major importance. Offline help without index and table of contents etc.
is not usable.

Kendy, why do you have to rush at this online solution for 3.3? I
propose to leave things as with OOo for 3.3, with help packs as separate
downloads if they are too big to be included in the international
package. In the meantime you can get the conversion procedures working
so that no metadata from help gets lost and on the road to 3.4 all the
teams and LO projects decide about the future of LO help system.
What you are driving at is having a non-fully-working solution for 3.3
with already some decision in place at very short notice (and such
decisions mostly lead to headache) and then decide for future. What I
propose is a fully working solution for 3.3 with enough time later to
decide and make a new system working fully for the 3.4 release.


From what I've understand, we will have normal HC2 files aside with 
3.3. Only the wikihelp will be in en_US. Then, the wikihelp will be 
implemented in all languages, but it has not to follow the release 
cycle. Only the HC2 and the porting from wikihelp to HC2 will have.


Hope this helps.

Kind regards
Sophie

--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [Libreoffice] [libreoffice-l10n] Re: Embedded parts and wikihelp/HC2

2010-12-16 Thread Michael Meeks
Hi Martin,

On Thu, 2010-12-16 at 17:40 +0100, Martin Srebotnjak wrote:
 I think online help must be available in all languages - it is a
 stopper, if it isn't.

I agree. On the other hand - if there are bugs in the web help we can
improve the conversion continually to fix them without having to
re-build master and delay the release endlessly, IMHO.

I imagine Kendy is working hard at this and other problems, and hey -
if anyone else wants to jump into working on the tools with him it
should be do-able. I imagine it is quite possible to setup your own wiki
to play with the translation as of now if people want to help out.

HTH,

Michael.

-- 
 michael.me...@novell.com  , Pseudo Engineer, itinerant idiot



-- 
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [libreoffice-l10n] Untranslated extensions

2010-12-16 Thread Freek de Kruijf
Op woensdag 15 december 2010 05:48:25 schreef Sophie Gautier:
 On 15/12/2010 00:35, Andras Timar wrote:
  2010/12/14 Rimas Kudelisr...@akl.lt:
  No need to convert actually, Pootle supports .properties files natively.
  I've just slightly altered the names of all four (2 English and 2
  German) files, and they're good to go:
  http://translations.documentfoundation.org/projects/extensions/.
  
  Those who want to translate using Pootle should just ask to enable
  translating this project into their language, and that's about it.
  
  I'm glad that it is so easy with Pootle. Thanks, Rimas. Please enable
  hu, I'll give it a try.
 
 Same for FR, thank you :)
 
 Kind regards
 Sophie

Same for NL.

-- 
fr.gr.

Freek de Kruijf

-- 
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***



[libreoffice-l10n] Re: Embedded parts and wikihelp/HC2

2010-12-16 Thread Marc Paré

Le 2010-12-16 13:08, Martin Srebotnjak a écrit :



While that would also be nice to have, I think it is mandatory to explain
that during installation. And at the end of installation it would be nice to
have a link to download the language pack. At least for Windows and OSX,
that have a GUI installer.

Also installing LO on multiple systems should provide option to install also
the langpacks (I believe that is possible now, but maybe some more
automation should be provided, given that it is two packages that need to be
installed, not just one, the fully localized build, as with OOo).

Your solution is not usable for users in a working environment without
internet access or with limited internet access (some companies/government
agencies limit Internet access for security, procastrination etc. reasons).

Lp, m.



With regard to large scale implementation, I can perhaps add, as 
example, my particular situation where I have convinced some heads of 
departments at a local school board to look at the OOo as possible 
replacement for MSO. This board usually corresponds regularly with 
neighbouring boards. I had recently written to these same people 
suggesting a change from OOo consideration to LibreOffice, not realizing 
that the Help files were going to be an issue. The implementation of 
almost 10,000 computers servicing over 100,000 students is taken quite 
seriously.


IT was already a little unconvinced of the implementation of OOo (LO) 
but at least they were listening. If the help files are not implemented 
in other language setups (we have mostly English desktops, but French as 
well as heritage language weekend classrooms where some units are in 
different languages), this will definitely not sell our product. The 
added steps in implementation would not be well received by IT and will 
not be given consideration for LibreOffice implementation.


It often takes a couple of years to change large organisation mindsets. 
I have therefore taken the stance to back off my correspondence to these 
people in the hopes of seeing a resolution. Otherwise, I will pace my 
correspondence to coincide with LO 3.4. I am sure I will not be the only 
one doing this.


We need to be careful with our product if we are to be taken seriously.

Marc


--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***



Re: [libreoffice-l10n] Untranslated extensions

2010-12-16 Thread Rimas Kudelis

Good morning,

2010.12.16 18:22, Harri Pitkänen rašė:

2010/12/14 Rimas Kudelisr...@akl.lt:

Those who want to translate using Pootle should just ask to enable
translating this project into their language, and that's about it.

I'd like to translate the extensions using Pootle. Note that the main Finnish
translation of LibreOffice is handled outside Pootle and we'd like to keep it
that way for 3.3. But these extensions would help us (the Finnish team) to get
familiar with Pootle and perhaps switch to it for the rest of LibO in the
future releases.

I registered to Pootle with account hatapitk. Could you please add the
Extensions for LibO 3.3 project for Finnish and give me the necessary rights
needed for translation?


Finnish added to the project, and you now have all the necessary rights 
on Pootle.


If you have any questions, don't hesitate to ask here. One of the things 
people usually ask is why the translation is not saved upon pressing 
Next. That's because you have to press Submit to save it. ;)


Rimas

--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***


Re: [libreoffice-l10n] To make the (Vietnamese) translation to be taken from pootle

2010-12-16 Thread Rimas Kudelis

Hi,

2010.12.16 18:19, Nguyen Vu Hung rašė:

On Fri, Dec 17, 2010 at 1:10 AM, Rimas Kudelisr...@akl.lt  wrote:

I see you are already registered with Pootle. You now have all the necessary
permissions to translate to Vietnamese.

Yes, but I don't have time yet to translate.
Is there anything else that I have to do? Is that all the translation
we make on pootle
will be integrated into git?


Sorry, I'm not following what exactly you mean. If you want your 
translation integrated, you should have the translation. Other than that 
you're supposed to list your team in the wiki (done) and fill the add a 
YES or NO to the Pootle column of the Vietnamese line in the table on 
the Translation for 3.3 wiki page: 
http://wiki.documentfoundation.org/Translation_for_3_3 . Yes means you 
want your translation taken from Pootle, NO means you want to provide it 
using other means.


More info about the translation process for this particular release is 
given on the same wiki page: 
http://wiki.documentfoundation.org/Translation_for_3_3 .


Regards,
Rimas


--
Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***