I checked with "Ooo 3.0.0 RC1 Multilingual version Italian UI WIN XP: [OOO300m5
(Build9350)]"  and can confirm the reported problem, pls. see attached Copy of
some help contents (English strings in red).
A quick test (control sample) only showed those untranslated strings in help for
CALC.

Created attachment 56292 [details]
samples

I also checked with "Ooo 3.0.0 RC1 Multilingual version German UI WIN XP:
[OOO300m5 (Build9350)]" and saw no untranslated strings in corresponding HELP items.

setting target

I've checked some of the sample strings in the Pootle and the target strings are
in English in Pootle. It seems that several strings in scalc/01.po is in
English. Therefore it should be shown as English in builds.
I also checked the backup file in July 8th. I can make sure that this issue must
has been before that time because the strings are already in English. 

Not sure exactly why/when did it happen, however doubt that incorrect po file
were uploaded at a stage.

.

Andrea, can you/the team proceed translating the English strings in Pootle asap?

We can try and fix strings in Pootle.
But it would be much easier, quicker and less risky if someone can find, and
attach to this issue, the PO file (or, if not PO, any sensible format) for OOo
2.4.1: all wrong strings appear to be correctly translated there.

I don't have a snapshot of 2.4.1 but the tmx files (2.4 release) are still
available at:
http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx24/

The Italian Localization team is now taking care of this.

I confirm the problem seems affecting only /hc2/scalc/01.po

Some strings into this file are present even in 2.4 but they are not into the 
TM created from that translation.

I don't have anymore .po files of 2.4 so I cannot create a TM to get the job 
done quickly (there are ~1000 segments untranslated!).

Can someone provide us a FULL TM or the .po file or the corresponding TM from 
2.4 files?

Andrea provided me a link to the original 2.4.1 file but I am unable to 
convert it in .po format.

The file is here:http://www.plio.it/documents/localize-241-scalc-01.sdf.bz2

I'd like to convert it using oo2po (translate-toolkit) but i get strange 
errors.

Can someone help me?

Hi paolopoz,

I had a quick look into the sdf file. It seems that the format is not suitable
for oo2po. If you want to convert a sdf to po with oo2po, the sdf format should
be source-targer pairs, i.e. English-Italian pairs. I'm not sure how to extract
Italian strings from the localized sdf.

Is it possible to use the tmx for 2.4, whose link was provided by Rafaella?

The tmx provided by Rafaella do not contain the strings we need. They are
included in OOo 2.4.x but not present in that tmx...

I just want to get a tm from the files I have. If they are unuseful I ask for
someone to give me a complete tmx from 2.4 else a valid po/sdf file for creating
from it a useful tm.
Is this possible? Translating 1k strings in a few days is really hard for us.

Paolo, Frank is running a test and see how much we could possibly fix
automatically. It may still remain a part which needs to be fixed manually.
Please stay tuned, We will inform you about the results asap.

And here are the results,
I've reset status to changed for all HC2 scalc strings where the en-US is equal
to IT. Additionally I've imported final strings from 2.4.1 in the same area.

We have aprox. 15000 words to translate. This is a huge bunch!!!

I started a second try to identify old Italian strings inside the
import-history. But it seems to be a general problem that en-US strings were not
translated and declared as final. Here I want to name explicit the solver.xhp
which is nearly untranslated.

Added mh on CC.

Paolo, on July 8th we imported a file delivered as *translated* containing
Calc/01 English strings in the Italian target line.
Do you have any backups of files uploaded to Pootle beginning of July?

I have it, but they contain untranslated strings too.
Maybe I just discovered what happened. During the first handoff I assigned 
that file to a stranslator. She did not translate it completely, however she 
sended it back to me just to upload only translated strings. In fact that file 
contain all strings marked as translated even if they were not. I did not have 
the time to check it (or assign this duty to others) because it was the last 
day to upload files into Pootle. So I uploaded it anyway...
At last it's all my fault. It seems the problem is also due to the way OmegaT 
handle untranslated segments (Maybe this is why it is not so suitable for 
translating .po files).

At this point I think it's unuseful to work with the old file, which still 
contain 1000+ untranslated strings.
We were going to fix the last file. It would be useful a full tm of 2.4 
anyway, given that some translated strings in OOo 2.4 are not present in the 
tm.

Paolo, if you have something it doesn't harm to attach it anyway.

I still haven't understood what the situation is like after fma's work: can I
assume that everything which appeared correctly (i.e., in Italian) in OOo 2.4.1
now does the same in OOo 3.0-to-be?

If at least we got all strings from 2.4.1 back, including the three examples I
made at the beginning, we might maybe reconsider the priority of this issue. Is
it possible to know where these 1000+ remaining strings (or 15000 words) are? If
only a specific subset of the Italian help pages is untranslated, the problem
might have a smaller impact on users.

Hi,
I've started a new try to reduce the number of strings. I'm checking the latest
Pootle export by Aijin manually, but this needs a while. So please stay tuned.
May be it helps, we will see....
Frank

just for the records I did not merge any Italian strings into the cws
localization32. If we are able to solve this issue we need to merge them in a
new cws

To facilitate work, I'll expand here the 3 examples I mentioned in the first
comment. They are not completely suitable for automated search because I'm
copying and pasting from the OOo online help, so some formatting instructions
may be lost. But they might help with investigations.

Example #1 (ADESSO, funzione)
OOo 2.4.1 Italian:
  Esempio
  =ADESSO()-A1 restituisce la differenza della data in A1 fino ad oggi. 
  Formattate il risultato come cifra.
OOo 3.0-RC1 Italian:
  Esempio
  =NOW()-A1 returns the difference between the date in A1 and now. Format the 
  result as a number.

Example #2 (DATA, funzione)
OOo 2.4.1 Italian:
  In Strumenti - Opzioni - OpenOffice.org - Generale potete impostare il
  valore massimo per riconoscere l'anno di due cifre secondo il modello 20xx.
OOo 3.0-RC1 Italian:
  In Tools - Options - OpenOffice.org - General you can set from which year a
  two-digit number entry is recognized as 20xx.
(and more strings)

Example #3 (VALUTA, funzione)
OOo 2.4.1 Italian:
  Converte un valore numerico in un testo avente il formato valuta. Il valore
  viene inoltre arrotondato alle cifre decimali indicate. Nel campo di testo
  Valore va introdotto il numero razionale da convertire nel formato valuta.
  Volendo, si può anche digitare nel campo Decimali il numero delle cifre
  decimali da rappresentare nel formato valuta. In mancanza di tale valore
  vengono usate due cifre decimali. 
OOo 3.0-RC1 Italian:
  Converts a number to an amount in the currency format, rounded to a
  specified decimal place. In the Value field enter the number to be
  converted to currency. Optionally, you may enter the number of decimal
  places in the Decimals field. If no value is specified, all numbers in
  currency format will be displayed with two decimal places. 
(and more strings)

Created attachment 56469 [details]
Untranslated strings, wordcount 13815

Attached sdf file including all untranslated strings in online-help. Word count
is 13815.
Frank

fma: This still has my examples untranslated. And they are translated in 2.4.1.

I'll describe my intended procedure for my first example, starting with the
latest attached files:
$ grep two-digit HC_new_2008-09-12_it.sdf 
helpcontent2    source\text\scalc\01\func_date.xhp      0       help   
par_id3153222   174                     0       en-US   In \<item
type=\"menuitem\"\>Tools - Options - $[officename] - General \</item\>you can
set from which year a two-digit number entry is recognized as 20xx.            
                  2008-01-24 15:27:00.0
helpcontent2    source\text\scalc\01\func_date.xhp      0       help   
par_id3153222   174                     0       it      In \<item
type=\"menuitem\"\>Tools - Options - $[officename] - General \</item\>you can
set from which year a two-digit number entry is recognized as 20xx.            
                  2008-08-09 04:39:00.0

So, from here, i get the string id, which is "par_id3153222".

Then I take the SDF file distributed with OOo 2.4.1 sources
http://www.plio.it/documents/localize-241-scalc-01.sdf.bz2 and look for that id:
$ grep par_id3153222 localize-241-scalc-01.sdf | grep -e "[[:blank:]]it"
helpcontent2    source\text\scalc\01\04060102.xhp       0       help   
par_id3153222   174                     0       it      In \<emph\>Strumenti -
Opzioni - $[officename] - Generale\</emph\> potete impostare il valore massimo
per riconoscere l'anno di due cifre secondo il modello 20xx.                   
            2002-02-02 02:02:02
helpcontent2    source\text\scalc\01\func_date.xhp      0       help   
par_id3153222   174                     0       it      In \<emph\>Strumenti -
Opzioni - $[officename] - Generale\</emph\> potete impostare il valore massimo
per riconoscere l'anno di due cifre secondo il modello 20xx.                   
            2002-02-02 02:02:02

And here I get the proper translation, which does exist and is in the OOo 2.4.1
source files.

Isn't it possible to automatize this? Lots of strings could be recovered this
way. And it seems like a script/tool could just go through the ids in the first
file (the one provided by fma) and look for them in the 2.4.1 sources.

Yes, is under investigation. Hope we can get some more strings out of the 2.4.1,
but if the en-US strings were changed we will fail. But we will see.

Frank, if at least we could take the previous translation and mark the strings
as changed we would minimize the translation work and concentrate on
untranslated strings only.

Hi Rafaella,
agreed, try to do so. In the meantime I'll make a backup ;-)
Frank

Rafaella, I already have a file containing only the strings we need to 
translate (at least for hc2/scalc/01.po).
Here it is.

Created attachment 56478 [details]
Strings in hc2/scalc/01.po that need to be translated (or checked)

Created attachment 56479 [details]
New sdf file with pre-translation inside

Added new sdf file with some old strings which can be used as pre-translation
(suggestion by Rafaella). This may be speeds up translation process.

Cheers,
Frank

This sounds good. Checking the file and reverting.

Thanks! A rough and quick check shows that, out of ~910 strings, we only have
~60 strings to translate and ~850 to check. This matches my expectations.

Moreover, the strings to check seem already OK and the file is correctly
processable through oo2po (just a note which might explain the origin of the
problem: if strings were expected to be marked as "fuzzy" or "untranslated" in
the resulting PO file, they aren't; of course this time we will check all of
them anyway).

We will wait for input from Rafaella before proceeding. But, with the latest
file, I believe the Italian community can get the translation done by Monday.

Perfect: the Italian Community has my GO to proceed with the translation of the
untranslated strings. Thx!

Created attachment 56502 [details]
List of Italian functions macro-created with the m5

Created attachment 56503 [details]
List of English Calc functions macro-created with m5

Attached 2 spreadsheets with the Calc functions and the parameters to be used as
reference during translation/testing.

File in helpcontent2 /scalc/01.po fixed and uploaded to Pootle. A big thanks 
to all italian translators who worked hard during the whole weekend.

A BIG BIG THANK YOU from me as well!

The helpcontent2 /scalc/01.po has been downloaded, converted and gsi-checked and
fixed. Attaching.

Created attachment 56536 [details]
IT Calc fix

Ivo, please create a new l10n CWS for the Italian fix and work with Petr to get
the CWS approved as soon as possible. Thx! Also, please pass on the fix to Frank
to uopdate the internal database. Thx!

If a CWS has to be created, could it contain both this fix and the one for issue
93785?
It is a related change (here we fix translations in the Calc Online Help -mainly
Solver- and there we fix a single word corresponding to the menu item for
Solver) and it would be best to merge everything at the same time.

For tracking purposes:
There were a few minor errors (missing tags etc.) in the 01.po file that I fixed
in order to successfully gsicheck the backconverted sdf file. Attaching a zip
with 2 files, one containing the strings before fixing them, the other
containing the fixed strings.

Please note that the file attached by coni this morning (attachment 56536 [details]) as
well as Pootle already contain all these fixes, so no further action is necessary.

Created attachment 56540 [details]
fixed strings

Thank you very much to all of you! - Great community work, all changes imported
into the database.
Frank

Verified on Linux/x86 and Solaris/SPARC on a localisation32 cws build.

--> setting as verified

This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
http://download.openoffice.org/index.html
If you want to know more about the handling of fixed/verified issues =>
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues