Speller - en_GB V2.08 - 7-JAN-2014 - Fixes suggested by Andrea

2014-01-07 Thread Marco A.G.Pinto

  
  
Hello Andrea, Alexandro Colorado and all,

Here are the changes:

1) changelog.txt
Added that it was based on the non-obfuscated Mozilla version.

2) README_en_GB.txt
Added the text suggested by Andrea, which appeared in the original
.txt shipped with his OXT.

 3) Created a test ODT to check with the 2013-07-31 and with
  2014-01-01
https://dl.dropboxusercontent.com/u/30674540/test_words_speller_20140107.odt

4) Created the OXT with the requested changes
https://dl.dropboxusercontent.com/u/30674540/dict-en-marcoagpinto-20140107.oxt


PS- I noticed that removing and installing the previous EN OXT
and this one,
   sometimes the typos are not detected. Just if, even if I
removed all extensions, it is
 still using my version. I don't know why this is happening.

I think I followed all of Andrea's steps.

What shall I do now?

Thanks!

Kind regards,
 Marco A.G.Pinto
 

-- 
  
  



Re: Speller - en_GB V2.08 - 7-JAN-2014 - Fixes suggested by Andrea

2014-01-07 Thread Andrea Pescetti

Marco A.G.Pinto wrote:

1) changelog.txt ...
2) README_en_GB.txt


Good, changes look OK! But the version must be incremented too, it's 
still 2014.01.01 and this creates problems. In this case you can leave 
it as it is since you never released the 2014.01.01 version on the 
Extensions site.



3) Created a test ODT to check with the 2013-07-31 and with 2014-01-01
https://dl.dropboxusercontent.com/u/30674540/test_words_speller_20140107.odt


Nice, this will be very useful for testing. But it will be more useful 
if you cut it to a few lines, since you have the changelog for the full 
list of changes. Lines 185 and 741 will be perfectly OK. What I usually 
do is a small table with:


Word Expected result   OpenOffice 4.0.1  Dictionary 2014.01.01
stereophony  Accepted   Not Accepted Accepted
spongelike   Not Acccepted  Accepted Not Accepted
test Accepted   Accepted Accepted
abcxyz   Not Acccepted  Not AccceptedNot Acccepted

copy this to a table in an ODT file and you are done, and everybody can 
test very quickly.


(Also, it's not my dictionary, I never added or removed a single word; 
it's the OpenOffice 4.0.1 dictionary).



4) Created the OXT with the requested changes
https://dl.dropboxusercontent.com/u/30674540/dict-en-marcoagpinto-20140107.oxt


OK.


PS- I noticed that removing and installing the previous EN OXT and this
one, sometimes the typos are not detected.


This will need to be investigated. Remember that the bundled 
dictionaries are a special case of extension, since they are (if I 
recall correctly) installed with administrative rights.



I think I followed all of Andrea's steps.
What shall I do now?


Let's go on with the plan then. Here it is:

1) Fix changelog.txt and possibly README files. - DONE

2) In the meantime, I will take care that the extension 
http://extensions.openoffice.org/en/project/aoo-dict-en is reassigned to 
you (this usually takes some days) - DONE, I see it hasn't been 
reassigned yet, but you will probably see it reassigned very soon, like 
tomorrow.


3) Once the extension is reassigned, create a new release (this means: 
upload your latest OXT file to the Extensions site) for the dictionary 
and leave it unpublished under the Publishing options, so users 
won't be notified of the new release. Your release is thus not listed 
but available for download from a direct link.


4) Send a quick note to d...@openoffice.apache.org saying that you 
replaced the en-GB dictionary and that you are going to publish the new 
release; give them one week to test, specify clearly that they must set 
en_GB for testing and provide:
a) Link to the unpublished release (I can help you here if you don't 
know where to find it)

b) Link to ODT test file in your DropBox (the one I described above, item 2)

5) If you don't receive any bad feedback, go on and flag your release as 
published and you are done! And at that time I will also update the 
OpenOffice source code to use your updated extension. And, after one 
week or so, users will start to receive notifications that a new version 
of the English dictionary is available.


Regards,
  Andrea.

-
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org



Re: If you need more help for an OpenOffice translation effort...

2014-01-07 Thread Rob Weir
On Tue, Jan 7, 2014 at 1:40 PM, Andrea Pescetti pesce...@apache.org wrote:
 Rob Weir wrote:

 If you need more help for an OpenOffice translation effort please let me
 know.


 This will surely be welcome. But we are now in a (hopefully short) moment
 where some administrative operations (like exporting translations and
 creating users) are not working due to a problematic upgrade.

 So I would recommend to wait until
 https://issues.apache.org/jira//browse/INFRA-7160
 is fixed before making a call.


Maybe a good time to work on updating the NL websites, as we wait for Pootle...


 And then, it should be remembered that we are faster in loading into Pootle
 an existing translation (those listed at
 http://svn.apache.org/viewvc/openoffice/trunk/extras/l10n/source/ ; often
 they are 50-80% translated) than in supporting an entirely new language.


 This works especially well if you
 already have a volunteer willing to take the lead on coordinating the
 translation effort.


 So far we are having good results even with having one motivated volunteer
 for some languages. Anyway, we could use these channels to enlarge the teams
 too.


I mean, if we call for more volunteers for a language, it will work
best if we have a more experienced existing volunteer willing to help
coordinate the new volunteers.  And even if one person could do the
work, it is more sustainable if we have a 2 or 3 involved.  Otherwise
we risk having a language appear in on release, but not another
release, if the sole translator is busy with school, work, family,
etc.   It is almost impossible to have too much help.  Well, except
when Pootle is not working ;-)

-Rob

 Regards,
   Andrea.

 -
 To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: l10n-h...@openoffice.apache.org


-
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org



Remove NLC icon from native-lang page and fix links

2014-01-07 Thread Tae Wong
The page: http://www.openoffice.org/native-lang/

uses a file that is a dead server:
http://contributing.openoffice.org/_media/language.png

Fix links.

These are listed here: http://qa.openoffice.org/localized/index.html
to:
These are listed here: http://www.openoffice.org/qa/localized/index.html

-
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org