You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Jürgen Schmidt <jo...@gmail.com> on 2013/05/13 15:24:11 UTC
[RELEASE][TRANSLATION]: changes to the README file for 4.0
Hi,
Ariel created a valid issue for updating the README file, a potential
further translation change, see
https://issues.apache.org/ooo/show_bug.cgi?id=122300
We need a native speaker who can update and polish the README based on
the input here from the list. The problem is that the README gets
generated and contains different content for each platform. See
http://svn.apache.org/viewvc/openoffice/trunk/main/readlicense_oo/docs/readme/readme.xrm?view=markup
Any volunteers or ideas how we can improve this?
I plan a last update for the translation at the end of this week.
Besides this and issue
https://issues.apache.org/ooo/show_bug.cgi?id=122265 we can do minor
changes until the end of this week, Friday 19th.
The new Pootle server should become available later this week when I
understand Jan correct. That means that we can and have to start and
push the translation starting with next week.
All the volunteers who have already started to work on the update can
hopefully reuse of their current work in a proper and efficient way. I
apologize for the confusion and bad coordination but I had many other
things to do and I am not happy with my own work ;-)
The good thing is that it becomes probably better in the future when we
the process get reworked.
But it also shows that we need some coordination and deadlines to
achieve our common goal and deliver releases in time.
Juergen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Andrea Pescetti <pe...@apache.org>.
Alexandro Colorado wrote:
> I did a quick read and I still think this language represent
> OpenOffice.org for example line 294:
> "...If you are not a developer, try the Documentation or the Marketing
> Project. "
> AFAIK we no longer have projects, so the areas are more related with
> other words like "mini site, module, or wiki".
Right, thanks. Now fixed in
http://svn.apache.org/viewvc?view=revision&revision=r1484333
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Alexandro Colorado <jz...@oooes.org>.
On 5/19/13, Andrea Pescetti <pe...@apache.org> wrote:
> On 17/05/2013 Jürgen Schmidt wrote:
>>> https://issues.apache.org/ooo/show_bug.cgi?id=122300
>> this issue is still open and we should address it. I fixed the About
>> issue and plan to work on the README on Tuesday. Any input or help is
>> very much appreciated to speed up this work.
I did a quick read and I still think this language represent
OpenOffice.org for example line 294:
"...If you are not a developer, try the Documentation or the Marketing
Project. "
AFAIK we no longer have projects, so the areas are more related with
other words like "mini site, module, or wiki".
>
> I've committed an updated README so that at least we don't display
> outdated content. Now, depending on how you wish to proceed, the steps
> would be:
>
> 1) Juergen checks if there is something else to correct/add (I haven't
> added anything so far)
>
> 2) We ask the doc list for a native speaker to proofread the README
>
> 3) We start translation. So far, translation teams always used the full
> README file. If we want to port it to a PO file too (which might be
> helpful in the long run), the result of
> $ html2po -P readme.xrm readme.pot
> looks rather usable.
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: l10n-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://es.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Andrea Pescetti <pe...@apache.org>.
Jürgen Schmidt wrote:
> On 5/19/13 6:28 PM, Andrea Pescetti wrote:
>> 3) We start translation. So far, translation teams always used the full
>> README file. If we want to port it to a PO file too (which might be
>> helpful in the long run), the result of
> I think it is already a po file on Pootle
> aoo40/readlicense_oo/docs/readme.po
Right. So, if this week's PO file refresh captures it, translators will
immediately find the updated strings in their PO files.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Jürgen Schmidt <jo...@gmail.com>.
On 5/19/13 6:28 PM, Andrea Pescetti wrote:
> On 17/05/2013 Jürgen Schmidt wrote:
>>> https://issues.apache.org/ooo/show_bug.cgi?id=122300
>> this issue is still open and we should address it. I fixed the About
>> issue and plan to work on the README on Tuesday. Any input or help is
>> very much appreciated to speed up this work.
>
> I've committed an updated README so that at least we don't display
> outdated content. Now, depending on how you wish to proceed, the steps
> would be:
>
> 1) Juergen checks if there is something else to correct/add (I haven't
> added anything so far)
>
> 2) We ask the doc list for a native speaker to proofread the README
make sense when we have reworked the file completely
>
> 3) We start translation. So far, translation teams always used the full
> README file. If we want to port it to a PO file too (which might be
> helpful in the long run), the result of
I think it is already a po file on Pootle
aoo40/readlicense_oo/docs/readme.po
For now I can live with making it correct and updated (means not
outdated). But for the future it make sense if we think and work an
something new and better maintainable.
Thanks
Juergen
> $ html2po -P readme.xrm readme.pot
> looks rather usable.
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Jürgen Schmidt <jo...@gmail.com>.
On 5/23/13 7:33 PM, Rob Weir wrote:
> On May 21, 2013, at 2:39 AM, "Jürgen Schmidt" <jo...@gmail.com> wrote:
>
>> On 5/19/13 6:28 PM, Andrea Pescetti wrote:
>>> On 17/05/2013 Jürgen Schmidt wrote:
>>>>> https://issues.apache.org/ooo/show_bug.cgi?id2300
>>>> this issue is still open and we should address it. I fixed the About
>>>> issue and plan to work on the README on Tuesday. Any input or help is
>>>> very much appreciated to speed up this work.
>>>
>>> I've committed an updated README so that at least we don't display
>>> outdated content. Now, depending on how you wish to proceed, the steps
>>> would be:
>>>
>>> 1) Juergen checks if there is something else to correct/add (I haven't
>>> added anything so far)
>>>
>>> 2) We ask the doc list for a native speaker to proofread the README
>>
>> make sense when we have reworked the file completely
>>
>
> I volunteer to review/edit the English version prior to translation.
review is always good ;-) but the translation is already ongoing or even
finished by some fast volunteers
Juergen
>
>
>>
>>>
>>> 3) We start translation. So far, translation teams always used the full
>>> README file. If we want to port it to a PO file too (which might be
>>> helpful in the long run), the result of
>>
>> I think it is already a po file on Pootle
>>
>> aoo40/readlicense_oo/docs/readme.po
>>
>>
>> For now I can live with making it correct and updated (means not
>> outdated). But for the future it make sense if we think and work an
>> something new and better maintainable.
>>
>> Thanks
>>
>> Juergen
>>
>>
>>> $ html2po -P readme.xrm readme.pot
>>> looks rather usable.
>>>
>>> Regards,
>>> Andrea.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by FR web forum <oo...@free.fr>.
>> Crazy idea. What if we just made a sub domain for each release? Or
>> equivalently a path under ooo-site. Then we could have hard-coded
>> standard paths in the code and other systems like:
>> www.openoffice.org/release/<**version>/README
>> Could also do LICENSE, release notes, even the update notification XML
>> files
Don't forget native language project.
Maybe an URL like:
www.openoffice.org/<**lang>/release/<**version>/README
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Kay Schenk <ka...@gmail.com>.
On Sat, Jun 8, 2013 at 12:46 PM, Andrea Pescetti <pe...@apache.org>wrote:
> On 01/06/2013 Rob Weir wrote:
>
>> Crazy idea. What if we just made a sub domain for each release? Or
>> equivalently a path under ooo-site. Then we could have hard-coded
>> standard paths in the code and other systems like:
>> www.openoffice.org/release/<**version>/README
>> Could also do LICENSE, release notes, even the update notification XML
>> files
>>
>
> Sounds like a very good idea. I'm not sure we will be able to implement it
> in time for OpenOffice 4 (translations get in the way), but it could be
> setup with some basic information already for version 4 (and, if the
> hard-coded URLs in version 4 are different and cannot be changed at this
> stage, we could redirect them appropriately).
Maybe a quick and not too confusing fix for this for 4.0 --
redirect /welcome/readme.html (meta refresh, no need to do anything else)
-> (new) /welcome/readme_4.0.html
Make changes as appropriate to new doc.
>
>
> Regards,
> Andrea.
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<de...@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
-------------------------------------------------------------------------------------------------
MzK
"Normal is not something to aspire to, it is something to get away from."
-- Jodie Foster
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Andrea Pescetti <pe...@apache.org>.
On 01/06/2013 Rob Weir wrote:
> Crazy idea. What if we just made a sub domain for each release? Or
> equivalently a path under ooo-site. Then we could have hard-coded
> standard paths in the code and other systems like:
> www.openoffice.org/release/<version>/README
> Could also do LICENSE, release notes, even the update notification XML files
Sounds like a very good idea. I'm not sure we will be able to implement
it in time for OpenOffice 4 (translations get in the way), but it could
be setup with some basic information already for version 4 (and, if the
hard-coded URLs in version 4 are different and cannot be changed at this
stage, we could redirect them appropriately).
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by "Dennis E. Hamilton" <de...@acm.org>.
++++++1
One-click access, Yay!!
- Dennis
-----Original Message-----
From: Rob Weir [mailto:rabastus@gmail.com]
Sent: Saturday, June 1, 2013 06:44 PM
To: dev@openoffice.apache.org
Subject: Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
On Jun 1, 2013, at 3:55 PM, "Dennis E. Hamilton"
<de...@acm.org> wrote:
>
> +1
>
> The <version>-specific path on the site is also a fine way to locate the check-for-update target, since the release has its release <version>. It can also have human-readable (and localized) pages that provide update information to someone who visits on-line.
>
> The default page at those locations could provide anything important about those particular versions, including obsolescence by security updates, what release replaced it, how to still obtain it, etc.
>
Good point, especially if there is access via the Help menu or other
prominent place in the UI. It is a good way to reach out to our
users. If we had it with 3.4.1, for example, we could have added
updated information for things like the language updates or fixes for
the profile-related problems.
A strong form of online engagement with our users could be quite
powerful. Although we had 50 million downloads of AOO 3.4, engaged
users via the announcement list, Facebook, Twitter, etc., is only
around 15,000 users. Imagine if all 50 million had one click access to
the latest info on their installed AOO release?
-Rob
> - Dennis
>
>
> -----Original Message-----
> From: Rob Weir [mailto:rabastus@gmail.com]
> Sent: Saturday, June 1, 2013 08:55 AM
> To: dev@openoffice.apache.org
> Subject: Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
>
> [ ... ]
>
> Crazy idea. What if we just made a sub domain for each release? Or
> equivalently a path under ooo-site. Then we could have hard-coded
> standard paths in the code and other systems like:
>
>
> www.openoffice.org/release/<version>/README
>
> Could also do LICENSE, release notes, even the update notification XML files
>
> So a special website per release. Then when we do a new release we
> just do an svn copy to populate the new site, and update as needed.
> The code then points to appropriate dir based on build time version
> flag.
>
> -Rob
>
[ ... ]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Rob Weir <ra...@gmail.com>.
On Jun 1, 2013, at 3:55 PM, "Dennis E. Hamilton"
<de...@acm.org> wrote:
>
> +1
>
> The <version>-specific path on the site is also a fine way to locate the check-for-update target, since the release has its release <version>. It can also have human-readable (and localized) pages that provide update information to someone who visits on-line.
>
> The default page at those locations could provide anything important about those particular versions, including obsolescence by security updates, what release replaced it, how to still obtain it, etc.
>
Good point, especially if there is access via the Help menu or other
prominent place in the UI. It is a good way to reach out to our
users. If we had it with 3.4.1, for example, we could have added
updated information for things like the language updates or fixes for
the profile-related problems.
A strong form of online engagement with our users could be quite
powerful. Although we had 50 million downloads of AOO 3.4, engaged
users via the announcement list, Facebook, Twitter, etc., is only
around 15,000 users. Imagine if all 50 million had one click access to
the latest info on their installed AOO release?
-Rob
> - Dennis
>
>
> -----Original Message-----
> From: Rob Weir [mailto:rabastus@gmail.com]
> Sent: Saturday, June 1, 2013 08:55 AM
> To: dev@openoffice.apache.org
> Subject: Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
>
> [ ... ]
>
> Crazy idea. What if we just made a sub domain for each release? Or
> equivalently a path under ooo-site. Then we could have hard-coded
> standard paths in the code and other systems like:
>
>
> www.openoffice.org/release/<version>/README
>
> Could also do LICENSE, release notes, even the update notification XML files
>
> So a special website per release. Then when we do a new release we
> just do an svn copy to populate the new site, and update as needed.
> The code then points to appropriate dir based on build time version
> flag.
>
> -Rob
>
>
>
>>> 2) The README has many references to the Solaris platform, which is
>>> not supported in the release. Should that be migrated into a separate
>>> readme that would be distributed by the Solaris port?
>>
>> The Solaris-specific strings are not displayed on other operating systems (you will see CSS classes that are used to suppress them at the above URL). That said, they are probably outdated and irrelevant indeed. I didn't move strings since it might have had an impact on translation.
>>
>> Regards,
>> Andrea.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by "Dennis E. Hamilton" <de...@acm.org>.
+1
The <version>-specific path on the site is also a fine way to locate the check-for-update target, since the release has its release <version>. It can also have human-readable (and localized) pages that provide update information to someone who visits on-line.
The default page at those locations could provide anything important about those particular versions, including obsolescence by security updates, what release replaced it, how to still obtain it, etc.
- Dennis
-----Original Message-----
From: Rob Weir [mailto:rabastus@gmail.com]
Sent: Saturday, June 1, 2013 08:55 AM
To: dev@openoffice.apache.org
Subject: Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
[ ... ]
Crazy idea. What if we just made a sub domain for each release? Or
equivalently a path under ooo-site. Then we could have hard-coded
standard paths in the code and other systems like:
www.openoffice.org/release/<version>/README
Could also do LICENSE, release notes, even the update notification XML files
So a special website per release. Then when we do a new release we
just do an svn copy to populate the new site, and update as needed.
The code then points to appropriate dir based on build time version
flag.
-Rob
>> 2) The README has many references to the Solaris platform, which is
>> not supported in the release. Should that be migrated into a separate
>> readme that would be distributed by the Solaris port?
>
> The Solaris-specific strings are not displayed on other operating systems (you will see CSS classes that are used to suppress them at the above URL). That said, they are probably outdated and irrelevant indeed. I didn't move strings since it might have had an impact on translation.
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Rob Weir <ra...@gmail.com>.
On Jun 1, 2013, at 10:55 AM, Andrea Pescetti <pe...@apache.org> wrote:
> On 29/05/2013 Rob Weir wrote:
>> On Fri, May 24, 2013 at 2:19 AM, Andrea Pescetti wrote:
>>> http://svn.apache.org/viewvc/openoffice/trunk/main/readlicense_oo/docs/readme/readme.xrm?view=log
>> I took a look. Two things that I noticed.
>>
>> 1) It refers the reader to this URL for the latest version of the README:
>> http://www.openoffice.org/welcome/readme.html
>> But that page does not appear to have been updated since OOo 3.0. Is
>> that URL correct? If so I can enter a BZ issue so we remember to
>> update the contents of that page with the latest README. On the other
>> hand, shouldn't this really be a per-version readme file?
>
> Yes, the web page must be updated before release. And, as for the per-version URL (like readme-400.html), this is a tradeoff to decide upon, since this requires manual changes at every release in all cases. So: either we "archive" old READMEs and link them from http://www.openoffice.org/welcome/readme.html or we use a specific URL. Considering string freeze and translations, it's probably better to do the former (archive the old ones) since it can be centralized and has a lesser impact on contributors.
>
Crazy idea. What if we just made a sub domain for each release? Or
equivalently a path under ooo-site. Then we could have hard-coded
standard paths in the code and other systems like:
www.openoffice.org/release/<version>/README
Could also do LICENSE, release notes, even the update notification XML files
So a special website per release. Then when we do a new release we
just do an svn copy to populate the new site, and update as needed.
The code then points to appropriate dir based on build time version
flag.
-Rob
>> 2) The README has many references to the Solaris platform, which is
>> not supported in the release. Should that be migrated into a separate
>> readme that would be distributed by the Solaris port?
>
> The Solaris-specific strings are not displayed on other operating systems (you will see CSS classes that are used to suppress them at the above URL). That said, they are probably outdated and irrelevant indeed. I didn't move strings since it might have had an impact on translation.
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Andrea Pescetti <pe...@apache.org>.
On 29/05/2013 Rob Weir wrote:
> On Fri, May 24, 2013 at 2:19 AM, Andrea Pescetti wrote:
>> http://svn.apache.org/viewvc/openoffice/trunk/main/readlicense_oo/docs/readme/readme.xrm?view=log
> I took a look. Two things that I noticed.
>
> 1) It refers the reader to this URL for the latest version of the README:
> http://www.openoffice.org/welcome/readme.html
> But that page does not appear to have been updated since OOo 3.0. Is
> that URL correct? If so I can enter a BZ issue so we remember to
> update the contents of that page with the latest README. On the other
> hand, shouldn't this really be a per-version readme file?
Yes, the web page must be updated before release. And, as for the
per-version URL (like readme-400.html), this is a tradeoff to decide
upon, since this requires manual changes at every release in all cases.
So: either we "archive" old READMEs and link them from
http://www.openoffice.org/welcome/readme.html or we use a specific URL.
Considering string freeze and translations, it's probably better to do
the former (archive the old ones) since it can be centralized and has a
lesser impact on contributors.
> 2) The README has many references to the Solaris platform, which is
> not supported in the release. Should that be migrated into a separate
> readme that would be distributed by the Solaris port?
The Solaris-specific strings are not displayed on other operating
systems (you will see CSS classes that are used to suppress them at the
above URL). That said, they are probably outdated and irrelevant indeed.
I didn't move strings since it might have had an impact on translation.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Rob Weir <ro...@apache.org>.
On Fri, May 24, 2013 at 2:19 AM, Andrea Pescetti <pe...@apache.org> wrote:
> On 23/05/2013 Rob Weir wrote:
>>
>> So did someone already review it? I don't want to duplicate effort if
>> this was already done. But since the readme is primary material for
>> journalists it would be good to have it polished.
>
>
> It's not primary material for journalists, probably, since it's a rather
> uninteresting file (properly done "Release Notes" would be what we want
> journalists to read).
>
> Anyway, nobody reviewed it after my last revision:
> http://svn.apache.org/viewvc/openoffice/trunk/main/readlicense_oo/docs/readme/readme.xrm?view=log
> So feel free to review the latest version there and commit the changes; if
> it is too late for translation, we can still use it for the online version.
>
I took a look. Two things that I noticed.
1) It refers the reader to this URL for the latest version of the README:
http://www.openoffice.org/welcome/readme.html
But that page does not appear to have been updated since OOo 3.0. Is
that URL correct? If so I can enter a BZ issue so we remember to
update the contents of that page with the latest README. On the other
hand, shouldn't this really be a per-version readme file? It might be
appropriate for an OOo 3.x users to still point to the 3.x README. So
maybe the URL in the README should be changed to readme-400.html or
something like that?
2) The README has many references to the Solaris platform, which is
not supported in the release. Should that be migrated into a separate
readme that would be distributed by the Solaris port?
Regards,
-Rob
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Andrea Pescetti <pe...@apache.org>.
On 23/05/2013 Rob Weir wrote:
> So did someone already review it? I don't want to duplicate effort if
> this was already done. But since the readme is primary material for
> journalists it would be good to have it polished.
It's not primary material for journalists, probably, since it's a rather
uninteresting file (properly done "Release Notes" would be what we want
journalists to read).
Anyway, nobody reviewed it after my last revision:
http://svn.apache.org/viewvc/openoffice/trunk/main/readlicense_oo/docs/readme/readme.xrm?view=log
So feel free to review the latest version there and commit the changes;
if it is too late for translation, we can still use it for the online
version.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Rob Weir <ra...@gmail.com>.
On May 23, 2013, at 1:41 PM, "Jürgen Schmidt" <jo...@gmail.com> wrote:
> On 5/23/13 7:33 PM, Rob Weir wrote:
>> On May 21, 2013, at 2:39 AM, "Jürgen Schmidt" <jo...@gmail.com> wrote:
>>
>>> On 5/19/13 6:28 PM, Andrea Pescetti wrote:
>>>> On 17/05/2013 Jürgen Schmidt wrote:
>>>>>> https://issues.apache.org/ooo/show_bug.cgi?id2300
>>>>> this issue is still open and we should address it. I fixed the About
>>>>> issue and plan to work on the README on Tuesday. Any input or help is
>>>>> very much appreciated to speed up this work.
>>>>
>>>> I've committed an updated README so that at least we don't display
>>>> outdated content. Now, depending on how you wish to proceed, the steps
>>>> would be:
>>>>
>>>> 1) Juergen checks if there is something else to correct/add (I haven't
>>>> added anything so far)
>>>>
>>>> 2) We ask the doc list for a native speaker to proofread the README
>>>
>>> make sense when we have reworked the file completely
>>
>> I volunteer to review/edit the English version prior to translation.
>
> review is always good ;-) but the translation is already ongoing or even
> finished by some fast volunteers
>
So did someone already review it? I don't want to duplicate effort if
this was already done. But since the readme is primary material for
journalists it would be good to have it polished.
Rob
> Juergen
>
>>
>>
>>>
>>>>
>>>> 3) We start translation. So far, translation teams always used the full
>>>> README file. If we want to port it to a PO file too (which might be
>>>> helpful in the long run), the result of
>>>
>>> I think it is already a po file on Pootle
>>>
>>> aoo40/readlicense_oo/docs/readme.po
>>>
>>>
>>> For now I can live with making it correct and updated (means not
>>> outdated). But for the future it make sense if we think and work an
>>> something new and better maintainable.
>>>
>>> Thanks
>>>
>>> Juergen
>>>
>>>
>>>> $ html2po -P readme.xrm readme.pot
>>>> looks rather usable.
>>>>
>>>> Regards,
>>>> Andrea.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Rob Weir <ra...@gmail.com>.
On May 21, 2013, at 2:39 AM, "Jürgen Schmidt" <jo...@gmail.com> wrote:
> On 5/19/13 6:28 PM, Andrea Pescetti wrote:
>> On 17/05/2013 Jürgen Schmidt wrote:
>>>> https://issues.apache.org/ooo/show_bug.cgi?id2300
>>> this issue is still open and we should address it. I fixed the About
>>> issue and plan to work on the README on Tuesday. Any input or help is
>>> very much appreciated to speed up this work.
>>
>> I've committed an updated README so that at least we don't display
>> outdated content. Now, depending on how you wish to proceed, the steps
>> would be:
>>
>> 1) Juergen checks if there is something else to correct/add (I haven't
>> added anything so far)
>>
>> 2) We ask the doc list for a native speaker to proofread the README
>
> make sense when we have reworked the file completely
>
I volunteer to review/edit the English version prior to translation.
>
>>
>> 3) We start translation. So far, translation teams always used the full
>> README file. If we want to port it to a PO file too (which might be
>> helpful in the long run), the result of
>
> I think it is already a po file on Pootle
>
> aoo40/readlicense_oo/docs/readme.po
>
>
> For now I can live with making it correct and updated (means not
> outdated). But for the future it make sense if we think and work an
> something new and better maintainable.
>
> Thanks
>
> Juergen
>
>
>> $ html2po -P readme.xrm readme.pot
>> looks rather usable.
>>
>> Regards,
>> Andrea.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Andrea Pescetti <pe...@apache.org>.
On 17/05/2013 Jürgen Schmidt wrote:
>> https://issues.apache.org/ooo/show_bug.cgi?id=122300
> this issue is still open and we should address it. I fixed the About
> issue and plan to work on the README on Tuesday. Any input or help is
> very much appreciated to speed up this work.
I've committed an updated README so that at least we don't display
outdated content. Now, depending on how you wish to proceed, the steps
would be:
1) Juergen checks if there is something else to correct/add (I haven't
added anything so far)
2) We ask the doc list for a native speaker to proofread the README
3) We start translation. So far, translation teams always used the full
README file. If we want to port it to a PO file too (which might be
helpful in the long run), the result of
$ html2po -P readme.xrm readme.pot
looks rather usable.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Andrea Pescetti <pe...@apache.org>.
On 17/05/2013 Jürgen Schmidt wrote:
>> https://issues.apache.org/ooo/show_bug.cgi?id=122300
> this issue is still open and we should address it. I fixed the About
> issue and plan to work on the README on Tuesday. Any input or help is
> very much appreciated to speed up this work.
I've committed an updated README so that at least we don't display
outdated content. Now, depending on how you wish to proceed, the steps
would be:
1) Juergen checks if there is something else to correct/add (I haven't
added anything so far)
2) We ask the doc list for a native speaker to proofread the README
3) We start translation. So far, translation teams always used the full
README file. If we want to port it to a PO file too (which might be
helpful in the long run), the result of
$ html2po -P readme.xrm readme.pot
looks rather usable.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Jürgen Schmidt <jo...@gmail.com>.
On 5/13/13 3:24 PM, Jürgen Schmidt wrote:
> Hi,
>
> Ariel created a valid issue for updating the README file, a potential
> further translation change, see
> https://issues.apache.org/ooo/show_bug.cgi?id=122300
>
> We need a native speaker who can update and polish the README based on
> the input here from the list. The problem is that the README gets
> generated and contains different content for each platform. See
> http://svn.apache.org/viewvc/openoffice/trunk/main/readlicense_oo/docs/readme/readme.xrm?view=markup
>
> Any volunteers or ideas how we can improve this?
>
>
> I plan a last update for the translation at the end of this week.
> Besides this and issue
> https://issues.apache.org/ooo/show_bug.cgi?id=122265 we can do minor
> changes until the end of this week, Friday 19th.
>
> The new Pootle server should become available later this week when I
> understand Jan correct. That means that we can and have to start and
> push the translation starting with next week.
>
> All the volunteers who have already started to work on the update can
> hopefully reuse of their current work in a proper and efficient way. I
> apologize for the confusion and bad coordination but I had many other
> things to do and I am not happy with my own work ;-)
>
> The good thing is that it becomes probably better in the future when we
> the process get reworked.
>
> But it also shows that we need some coordination and deadlines to
> achieve our common goal and deliver releases in time.
>
this issue is still open and we should address it. I fixed the About
issue and plan to work on the README on Tuesday. Any input or help is
very much appreciated to speed up this work.
The translation update will I trigger after the fix next week.
Juergen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [RELEASE][TRANSLATION]: changes to the README file for 4.0
Posted by Jürgen Schmidt <jo...@gmail.com>.
On 5/13/13 3:24 PM, Jürgen Schmidt wrote:
> Hi,
>
> Ariel created a valid issue for updating the README file, a potential
> further translation change, see
> https://issues.apache.org/ooo/show_bug.cgi?id=122300
>
> We need a native speaker who can update and polish the README based on
> the input here from the list. The problem is that the README gets
> generated and contains different content for each platform. See
> http://svn.apache.org/viewvc/openoffice/trunk/main/readlicense_oo/docs/readme/readme.xrm?view=markup
>
> Any volunteers or ideas how we can improve this?
>
>
> I plan a last update for the translation at the end of this week.
> Besides this and issue
> https://issues.apache.org/ooo/show_bug.cgi?id=122265 we can do minor
> changes until the end of this week, Friday 19th.
>
> The new Pootle server should become available later this week when I
> understand Jan correct. That means that we can and have to start and
> push the translation starting with next week.
>
> All the volunteers who have already started to work on the update can
> hopefully reuse of their current work in a proper and efficient way. I
> apologize for the confusion and bad coordination but I had many other
> things to do and I am not happy with my own work ;-)
>
> The good thing is that it becomes probably better in the future when we
> the process get reworked.
>
> But it also shows that we need some coordination and deadlines to
> achieve our common goal and deliver releases in time.
>
this issue is still open and we should address it. I fixed the About
issue and plan to work on the README on Tuesday. Any input or help is
very much appreciated to speed up this work.
The translation update will I trigger after the fix next week.
Juergen
---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscribe@openoffice.apache.org
For additional commands, e-mail: l10n-help@openoffice.apache.org