Hi everyone :) On 27/06/2008, at 2:16 AM, Charles-H. Schulz wrote:
Without dwelling too much on this, I think that what you describe is good, efficient, but falls behind the point. It would be better if each language could simply have the update notification on and working, regardless of Sun's coverage.[Joost] that would be possible if all build providers include that feature at build time. That is not the case. On the other hand the product update service requires manual interaction it does not work like magic.That's an important piece of information: it thus means that if Clytie's or Leif's builds have not the feature of automatic update notification working, it is because it was not included at build time and/or it's not been activated.
Exactly. It doesn't mean they're incapable of that feature, if I have understood the explanations correctly. I'm interested in the reminder that our completing our Help translation means we will finally get complete builds from Sun, but as you point out, that doesn't help the teams who haven't been as lucky.
Actually, I hope for a fairly wide-reaching improvement to Sun's build process, because we also need more frequent builds. Pavel's community builds provide dynamic feedback: he builds much more frequently, and accepts updated translations. Sun only accepts translations once or twice per version. Pavel will accept an updated translation for every build, which means up to twice a week!
Effectively, Pavel's builds are more recent, from both the software and the localization points of view.
We have to distinguish two levels of notification (NB: I'm not talking about the automatic, incremental update that we do not have on OOo): - notification of the new version regardless of the localization readiness. That could even be configured automatic update of developers' build (see Firefox)That should already be the case for en-US developer snapshots. Language packs are not notified (AFAIK).- notification of the new, localized version which ultimately rests on the localized build maintainer's ability to launch the notification procedure.Update notification of releases can be done if 1. the build has the update notification feature included/activated 2. the build has been distributed to the mirrors 3. a) the Bouncer links work b) a localized landing page is available eg. http://update.services.openoffice.org/ooo/index_fr.html 4. the build has been tested and approved for distributionI think that's what the issue here. Do you think we can change it?If there would be enough disk space on the mirror network I believe Sun could provide a lot of more localizations as full builds and it would be possible to lower the requirements to get a full build.Thank you for these ideas. I think -but others are welcome to comment- that the problem is not that Sun does or does not provide all the builds, it is that the feature at handshall always be included at build time and activated (for sake of clarity, do you have any how-to for those two actions?). We need to work on that first. The propagation to the mirrors, the bouncer question and the release clearance are pretty obvious perequisites I think but I may be wrong.
Yes, activation comes first. Once we have that ready to occur, we can provide the extra resources required. A localized landing page could be created very quickly, if we were able to access the original text, and submit the translation.
from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n
PGP.sig
Description: This is a digitally signed message part
