Apache OpenOffice (AOO) Bugzilla – Issue 87671
[IT] Harmonization of the translation of the term "sheet" in Italian (Tabella --> Foglio)
Last modified: 2013-08-07 15:02:29 UTC
In the Italian localization the term "sheet" is translated, both in the UI and on line help in two different ways, i.e. "tabella" or "foglio". It was lately agreed that "foglio" is a better translation. As both the singular and plural will have to be replaced would it be possible to produce three .sdf files as follows? 1. a file with all the strings containing the word "sheet", but not the word "sheets" 2. a file with all the strings containing the word "sheets" but not the word "sheet" 3. a file with the strings containing both the words "sheet" and "sheets". This way the files should have a 0 intersection making the implementation easy. Cheers, Michele
... made a mistake in the classification... The issue is l10n not spreadsheet... Cheers, Michele
*** Issue 87671 has been confirmed by votes. ***
Can you please reassign to petr_dudacek? Cheers, Michele
*** Issue 88819 has been marked as a duplicate of this issue. ***
Taking over this one... -> reassign to myself
setting target
Asked Frank for the sdf files via email... waiting for a reply.
Created attachment 54263 [details] sdf file with sheet only content
Created attachment 54264 [details] sdf file with sheets only content
Created attachment 54265 [details] sdf file with sheet and sheets content
Hope these three files fulfill your expectations. If not let me know. Frank
A few questions: once modified, how can we manage to merge the strings with Pootle content? Whitin tomorrow we will have the new strings (dev300_m17) available on the server. Do I have to wait assigning them?
Hello *, If I understand correctly all these strings have already been translated, so it should be safe to correct the issue and integrate them in the database. The only recommendation is to make sure that the localization team knows that they have to translate correctly the terms sheet/sheets from now on. I will send a message also to assess how we can split up the work (1000+ strings to be corrected. Cheers, Michele
Petr, if you and the IT Community fix the issue on sdf files which are extracted out of the internal DB they a) will be overwritten when we will import the files from Pootle on July 4th b) will now be imported into Pootle. Pootle has the most updated translations, files extracted from the internal DB do not reflect the latest status. The terminology inconsistency should be fixed in Pootle otherwise the IT Community risks to work for nothing.
Hello coni, In general I agree with you but in this particular instance I respectfully disagree. The Italian l10n team is already fixing this issue in the *new* strings for OOo3.0 so the implementation of the changes on the "legacy" DB will be even more important now in order to achieve consistency. BTW: Valter already did the bulk of the work (1500 out of 2136 strings), so the fix should become available by the end of this week. Cheers, Michele
Michele, may be I was not clear. The issue here is a process issue where it is very important to do the right process steps in the right sequence. We are not updating Pootle with the DB content but vice versa. In summary: what is fixed in Pootle will be automatically fixed in the internal DB and will be integrated into the builds.
.
Hello I totally agree that we have to manage the process carefully and I am quite aware of the problem as you can see here: http://wiki.services.openoffice.org/wiki/Talk:Handling_Translation_Issues (25th Oct last year). What I am saying is that this is a special case that can be handled a bit differently given the special circumstances. Please take a look at the rest of the comment and let me know if you spot a mistake. Cheers, Michele Assumptions ----------- 1) A small part of the strings to be fixed for this issue have also been provided to the localization team. 2) The localization team knows that they have to translate the term "sheet" as recommended in this issue Process ------- 1) the corrected strings for this issue are input in the DB before step 2. 2) the DB is updated with the new strings coming from pootle Note: given assumption 1 some of the strings provided in the .sdf files for this issue will be overwritten when the pootle strings get integrated, but given assumption 2 this is OK. Result ------ The issue is fixed both for the "legacy" strings and for the new strings.
Hi Michele, to me, the most straightforward process seems to be: 1. take the .sdf files from Frank and convert them to .po 2. translate the .po files offline 3. upload the translated .po files to Pootle This way, we would avoid uploading content to the translation database from two different sources. Just my 2 cents, Petr
Michele, after an offline discussion with Rafaella, we came to the agreement that the process I outlined would bring some consistency issues, therefore please ignore what I proposed. Thanks, Petr
Is it possible to extract these strings directly from pootle content when all the .po files will be translated? If so, we can provide translated strings during the week, then resolve this issue by friday.
Hello *, Translating with pootle is a royal pain since it is not possible to use global search & replace, so I suggest to wait until the 4th of July, create again the sdf against the latest version of the database and sort out the issue quickly before the next round of translation. The negative effect is that the issue will not be solved for another x months, but at least we do not risk ending up with conflicting versions of the same string. Cheers, Michele
Please continue working on the SDF file as originally delivered to fix the issues. And redeliver back to us once done. The process will be: 1. import Pootle translations into the internal DB 2. import SDF files with corrections into the internal DB 3. full export content from DB 4. full reupload of IT content to Pootle
Hi Michele, what is the status of your work on this issue? To have the changes in 3.0, we need to have the sdf file back until the end of this week. Next Monday is the very very latest date. Thanks, Petr
Hello Petr, Would it be possible to re-generate the SDF files now that the Italian l10n team has finished translating? this would avoid overwriting of the newly translated strings with the strings to be corrected to solve this issue. If the new strings from the Italian team have not been integrated yet, then it may be safer to leave the issue open and fix it later (between two translation cycles). Once the strings are available it should be feasible to finish in three days, so if you are quick and give us the strings tomorrow they will be back Monday. Cheers, Michele
Hi Michele, the latest strings from Pootle are not in the translation database yet. The integration will take place tomorrow (Friday, July 4). So the sdf files can be ready right after the integration. Is it still ok for you? Just let me know. Thanks, Petr
Hello, I guess it will be a bit tight, but it is worth a try. I will send a message to the Italian localization group now to see if I can gather a couple of volunteers willing to spend part of their weekend doing some search & replace. Cheers, Michele
We didn't get the sdf files on time :( Need to retarget to 3.1. Apologies for that... -> target 3.1
retargetting to 3.0. Due to the 2 weeks roadmap delay, we can still make it. Paolo, as discussed offlist, please go ahead and use http://translate.sourceforge.net/wiki/toolkit/pogrep to fix the terminology as needed. Once you/ the IT team has finished and the corrections uploaded to Pootle, please reassign this issue to blueice7. Thx!
Translated strings uploaded to Pootle. Reassigning to Aijin as requested by Rafaella.
All the content of Italian in Pootle was delivered on July 31th.
Reopening: a few, very visible, strings were wrong and have now been fixed in Pootle.
fixed on master