RE: Proofing Tool GUI 3.0 - beta - build 100 - 2017-01-01 Released

[Dennis E. Hamilton]

> -Original Message-
> From: Marco A.G.Pinto [mailto:marcoagpi...@mail.telepac.pt]
> Sent: Sunday, January 1, 2017 09:11
> To: Mailing List - AOO - l10n 
> Subject: Proofing Tool GUI 3.0 - beta - build 100 - 2017-01-01 Released
> 
> Hello!
> 
> Just to announce that I have updated PTG for Windows and Linux.
> 
> It can be downloaded from its official site:
> http://marcoagpinto.cidadevirtual.pt/proofingtoolgui.html
[orcmid] 

Marco,

Thank you for your continued devotion to providing quality English-language 
writing aids.

It is great to see the dictionary work on GitHub.  Perhaps someday PTG will 
also be available there.

> 
> The latest build has the GUI improved a lot and also accepts items
> multiselection and to choose the window size: 1024x600 or 1280x600.
> 
> 
> In the next update I will try to implement GTK3 support (Linux) and
> allow undo/redo like Shantanu suggested.
> 
> Also, notice the extra tabs which are still not working but they mean
> that in a future version it will be possible to edit/create rules for
> LanguageTool and have language specific operations (text processing).
> 
> Does anyone know where I can get an hyphenator so that I see how it
> works and can code its tab in PTG? This tab has been blank for years.
[orcmid] 

I don't have the details, but many use the Frank Liang hyphenator that was 
created for TeX (and LaTeX).  

.

It would be nice to have a model that worked in UTF-8 and distinguished between 
hard and soft hyphenation.

Meanwhile, have a Happy New Year and continued satisfaction in your worthy 
endeavors in providing writing aids.

 - Dennis


> 
> PS->Notice that I added some persons in Bcc in this e-mail.
> 
> Thanks!
> 
> Kind regards from the English Dictionaries maintainer,
>   >Marco A.G.Pinto
> --
> 
> 
> --



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

RE: [PROPOSAL] General Availability of ApacheOpenOffice 4.1.2-patch1 Hotfixes

[Dennis E. Hamilton]

[BCC to PMC, FYI to L10N and QA.]

The 4.2.1-patch1 release repository is now populated with the only 
localizations that we have: English (en-US) and German (de) for all platforms 
plus the additional Nederland (nl) for Windows.  The localizations took until 
yesterday, 2016-08-25, to be completed.

Propagation to the archive site has begun and will probably not be complete for 
another 24 hours.  Meanwhile, an updated CVE-2016-1513 will be prepared.  The 
update will be posted when the archive is stable, along with notification to 
dev@ and users@.  Those actions will provide the general availability of the 
Hotfix.

While minor blemishes may remain, this material will be kept stable as is 
unless a serious defect is brought to our attention.  Cosmetic matters are 
appropriate to save for whenever we need to do this again.

One lesson: Localizations should not hold up release in the future.  
Localizations not available during the initial dev QA and review period should 
not stop the train.  Supplemental localizations are always possible.  That will 
likely always be the case when a hotfix is made available along with an initial 
vulnerability disclosure and advisory.

 - Dennis

> -Original Message-
> From: Dennis E. Hamilton [mailto:orc...@apache.org]
> Sent: Friday, August 19, 2016 15:02
> To: d...@openoffice.apache.org
> Subject: [PROPOSAL] General Availability of ApacheOpenOffice 4.1.2-
> patch1 Hotfixes
> 
> [BCC PMC, FYI QA]
> 
> At this time, the preparation and dev@/qa@ confirmation of the AOO
> 4.1.2-patch1 Hotfixes has quieted.
> 
> I propose that the current binaries be placed into general availability.
> I am initiating lazy consensus to end not before Tuesday, 2016-08-
> 23T22:00Z.
> 
> MATERIALS TO BE AVAILABLE
> 
>  * The file hotfix.html at
><https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch1/>
>will be made available at
><https://archive.apache.org/dist/openoffice/4.1.2-patch1/>
> 
>  * The directory folder
><https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/binaries/>
>will be made available as a subdirectory of
><https://archive.apache.org/dist/openoffice/4.1.2-patch1/>.
> 
> ANNOUNCEMENT OF AVAILABILITY
> 
>   * The CVE-2016-1513 advisory,
> <http://www.openoffice.org/security/cves/CVE-2016-1513.html>,
> will be reissued to include availability of the hotfix and
> refer users to the hotfix.html page in the archive 4.1.2-patch1
> location.
> 
>   * There will be an accompanying announcement on dev@, users@,
> and in the two bugzilla issues related to the defect that the
> hotfix applies to.
> 
> WHAT TO REVIEW
> 
> You can find everything to be made available by starting with the
> hotfix.html page at
> <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/hotfix.html>.
> 
> IGNORE the Source column.  The source release has already occurred, and
> those links will not be valid until deployment of hotfix.html to the
> archive location.
> 
> The README files are the next materials to examine.  There you can learn
> more about the hotfix for each of the four platforms: Windows, MacOSX,
> Linux32, and Linux64.  Follow any of the procedures that you want to
> verify.
> 
> 
>  - Dennis
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


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

RE: [DISCUSS] Release 4.2: General Topics

[Dennis E. Hamilton]

The problem of incomplete shutdown is very serious.  It can result in damaged 
and completely lost in-progress work, even though apparently saved, and other 
damage.  The whole problem of shutdown, Quickstarter, and failed auto-recovery 
is a big ball of snakes that is worthy of a maintenance release all on its own.

With regard to spell-checking, the usual symptom is that suddenly all words are 
redlined.  Having it stop checking probably goes unnoticed more often, as it 
did for Don.

With regard to spell-checking, there is a promise to provide a profile-fix tool 
for Windows, 
.  That is a bit buried 
(but look at the issue it is tied to). 

I will open a separate task for this now.

At some point, installation of such a tool should at least be part of the built 
distribution.

So there are three steps:

 1. Get the tool out there as something users can install and use.

 2. Incorporate the tool in our binary distributions.

 3. Fix the shut-down problems we have that are so overwhelming and so damaging 
to the work of our users.

Steps (1) will require QA work and L10N work in order to reach the greatest 
number of users.  English will only work for 45% of our users.  It should work 
better for end users than the instructions that are being provided repetitively 
each time someone stumbles on this and manages to report it.   

This is clearly a triage situation.  We need something now, we need something 
about best practices, such as having Quickstarter OFF by default at least on 
Windows, and also doing something about auto-recovery failures.  And we can't 
wait for laborious software fixes for which there is no foreseeable developer 
availability and then production of subsequent full-binary distributions.

Speaking of triage, the targeting of Windows reaches 87% of our users based on 
platform downloads.  Remedies there are assisted by the fact that cmd.exe (the 
console processor) and command-line utilities are available on all versions of 
Windows that AOO supports.  In addition, every install of AOO includes a 
functional version of Python in the OpenOffice 4 code.  Accomplishing the 
provision of side-car utilities for other platforms will depend on committers 
who are devoted to those platforms stepping forward.

 - Dennis

PS: The 4.1.2-patch1 Hotfix will roll to general distribution in the next 24-48 
hours.  We have English language covered and there is provision for more L10N 
localization.  However, the only one completed at this time is Nederland (nl, 
Dutch) for the Windows version.  A Deutsch (de, German) one is in the works.  
To get better coverage, the priority additional L10N-s should be French, 
Italian, and Spanish.  That gets us to 75% of the users by downloaded 
languages.  To get to 90% add Japanese, Russian, Polish, (Dutch), and 
Portuguese.  Chinese would be a great bonus and, of course, we would appreciate 
any other localizations that AOO enthusiasts and committers provide. 

> -Original Message-
> From: Don Lewis [mailto:truck...@apache.org]
> Sent: Wednesday, August 24, 2016 00:38
> To: ofarr...@iol.ie
> Cc: d...@openoffice.apache.org; q...@openoffice.apache.org;
> l10n@openoffice.apache.org
> Subject: Re: [DISCUSS] Release 4.2: General Topics
> 
> On 24 Aug, Rory O'Farrell wrote:
> > On Wed, 24 Aug 2016 00:01:22 -0700 (PDT)
> > Don Lewis  wrote:
> 
> >> Someone should fix the broken spellcheck problem.  It generates a lot
> of
> >> complaints from our users.
> >>
> >
> > The "broken spellcheck problem" seems largely to be caused by over
> hasty close-down of the computer before cached files (both hardware and
> software caches) are properly written to disk.  User education is the
> answer - educate them to be patient in closedown and wait for disk
> activity to finish before power-off.
> 
> Maybe using fsync() to flush things out faster when shutting down the
> app and keeping a backup copy of the config would help avoid the
> problem.   We shouldn't just silently fail when something is corrupt.
> 
> I've even experienced this myself on my FreeBSD desktop which stays on
> 24x7 and has an UPS.  It took me quite a while to notice spellcheck
> wasn't working.  I just thought my spelling was unusually good ;-)
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


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

RE: [PROPOSAL] General Availability of ApacheOpenOffice 4.1.2-patch1 Hotfixes

[Dennis E. Hamilton]

[BCC PMC, FYI QA and L10N]

There have been no comments concerning the placement of the current materials 
into general distribution.

In addition, there is a set of Dutch (Nederland) language that also passes all 
tests and has been carefully proof-read.  These have been added to the 
directory folder.  (They are not reflected in the hotfix.html so far.)

A set of German (Deutsch) language scripts has been prepared and had to be 
changed from Unicode (UTF8) to ISO 8859-1 (Western European) in order to run 
properly on Windows XP.  The script window does not show extended characters 
used in German on an English Windows XP, but the scripts run correctly.  They 
should appear correctly in Windows XP installs set for Western European 
languages.  This part remains to be confirmed.  See 
<https://bz.apache.org/ooo/show_bug.cgi?id=127082>.

If the German version is not complete today, I propose going ahead with the 
general distribution of the English and Dutch ones and adding the German set 
later.

 - Dennis



> -Original Message-
> From: Dennis E. Hamilton [mailto:orc...@apache.org]
> Sent: Friday, August 19, 2016 15:02
> To: d...@openoffice.apache.org
> Subject: [PROPOSAL] General Availability of ApacheOpenOffice 4.1.2-
> patch1 Hotfixes
> 
> [BCC PMC, FYI QA]
> 
> At this time, the preparation and dev@/qa@ confirmation of the AOO
> 4.1.2-patch1 Hotfixes has quieted.
> 
> I propose that the current binaries be placed into general availability.
> I am initiating lazy consensus to end not before Tuesday, 2016-08-
> 23T22:00Z.
> 
> MATERIALS TO BE AVAILABLE
> 
>  * The file hotfix.html at
><https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch1/>
>will be made available at
><https://archive.apache.org/dist/openoffice/4.1.2-patch1/>
> 
>  * The directory folder
><https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/binaries/>
>will be made available as a subdirectory of
><https://archive.apache.org/dist/openoffice/4.1.2-patch1/>.
> 
> ANNOUNCEMENT OF AVAILABILITY
> 
>   * The CVE-2016-1513 advisory,
> <http://www.openoffice.org/security/cves/CVE-2016-1513.html>,
> will be reissued to include availability of the hotfix and
> refer users to the hotfix.html page in the archive 4.1.2-patch1
> location.
> 
>   * There will be an accompanying announcement on dev@, users@,
> and in the two bugzilla issues related to the defect that the
> hotfix applies to.
> 
> WHAT TO REVIEW
> 
> You can find everything to be made available by starting with the
> hotfix.html page at
> <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/hotfix.html>.
> 
> IGNORE the Source column.  The source release has already occurred, and
> those links will not be valid until deployment of hotfix.html to the
> archive location.
> 
> The README files are the next materials to examine.  There you can learn
> more about the hotfix for each of the four platforms: Windows, MacOSX,
> Linux32, and Linux64.  Follow any of the procedures that you want to
> verify.
> 
> 
>  - Dennis
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


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

RE: FW: Internationalization of 4.1.2-patch1 (was RE: a question about "APPLY-4.1.2-patch1.bat")

[Dennis E. Hamilton]

[Please cross-post all replies]

Two localizations for the 4.1.2-patch1 hotfix are near completion.  

   They are for German (de) and Nederlands (nl) (often "Dutch" in English). 

It would be very useful to have localizations in French, Italian, and Spanish, 
preferably by native speakers.

NAMING THE FILES

Unfortunately, the English-language README and the download file have no 
language suffix.  They are

README-4.1.2-patch1-Windows.txt
and apache-openoffice-4.1.2-patch1-Win_x86.zip

Also, the install and uninstall script names do not reflect their language:

APPLY-4.1.2-patch1.bat
and REVERT-4.1.2-patch1.bat

LOCALIZED NAMING

For the additional localizations, language suffixes are proposed to an aid in 
multilingual situations and to prevent name collisions.  With suffixes, the 
relevant names would become (using German for example),

  README-4.1.2-patch1-Windows-de.txt
  Apache-openoffice-4.1.2-patch1-Win_x86_de.zip
  APPLY-4.1.2-patch1_de.bat
  REVERT-4.1.2-patch1_de.bat

In reviewing the localizations, I will adjust these as needed.

 - Dennis



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

RE: FW: Internationalization of 4.1.2-patch1 (was RE: a question about "APPLY-4.1.2-patch1.bat")

[Dennis E. Hamilton]

[Please always include dev@ in replies on this topic.]

> -Original Message-
> From: Dick Groskamp [mailto:th.grosk...@quicknet.nl]
> Sent: Sunday, August 21, 2016 08:26
> To: l10n@openoffice.apache.org
> Cc: d...@openoffice.apache.org
> Subject: Re: FW: Internationalization of 4.1.2-patch1 (was RE: a
> question about "APPLY-4.1.2-patch1.bat")
> 
> Op 20-8-2016 om 21:49 schreef Dennis E. Hamilton:
> > https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> > >patch1/hotfix.html
> I've translated README, APPLY.bat (messages) and REVERT.bat (messages)
> into Dutch
> 
> I've adjusted the page Jörg made at CWIKI with a table to register
> translations.
> 
> Two questions though:
> 
> 1. do you only need the messages from APPLY.bat and REVERT.bat or can I
> sent the complete file somewhere ?
> 
> 2. where do I put the translations. I'm not that a tech savvy
[orcmid] 

 1. Complete files are fine.  We can diff them to check them against the 
originals.

 2. Open a task issue (e.g., Dutch Language Windows 4.1.2-patch1 files) on the 
Bugzilla and submit your files as attachments.  This provides a place for their 
review and also any updating.

NOTE: If you use any special characters beyond the ISO 7-bit (ASCII) set, be 
certain to have your files in UTF-8.

 - Dennis


> 
> 
> Greetings
> 
> --
> DiGro
> ___
> Apache OpenOffice 4.0.1 (Dutch) and scanned with Ziggo extended security
> (F-Secure)
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


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

RE: Internationalization of 4.1.2-patch1 (was RE: a question about "APPLY-4.1.2-patch1.bat")

[Dennis E. Hamilton]

[BCC to l10n list]

> -Original Message-
> From: Jörg Schmidt [mailto:joe...@j-m-schmidt.de]
> Sent: Saturday, August 20, 2016 15:32
> To: d...@openoffice.apache.org; dennis.hamil...@acm.org
> Subject: Re: Internationalization of 4.1.2-patch1 (was RE: a question
> about "APPLY-4.1.2-patch1.bat")
> 
> Hello,
> 
> > From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> 
> > All of the information on the release of 4.1.2-patch1,
> > including readmes and messages from the patch install and
> > uninstall scripts, is in English.  See
> > <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-patch
> > 1/hotfix.html> and the Readme files.  Also, the Windows
> > package contains install and uninstall scripts that provide
> > messages in English.
> >
> > It would be useful for there to be internationalization of
> > the texts and messages, especially for the Windows version.
> >
> > If the proportion of languages chosen for downloads is an
> > useful guide,
> >
> > English language is selected for over 40% of downloads.
> >
> > If French, German, Italian, and Spanish were also supported,
> > then a total of 75% of all downloads would be covered.
> >
> > To reach 90%, add Japanese, Russian, Polish, Dutch, and
> > Portuguese (BR).
> >
> > Supplementing the 4.1.2-patch1 files in this manner is
> > possible, if committers are willing to provide translations.
> > To submit a translation for the Windows case, we need a
> > translation of the README and of the text messages presented
> > by the APPLY and REVERT scripts in the Zip for Windows.
> > These must be supplied by an OpenOffice committer who can
> > provide a PGP signature on their submission, or they must be
> > submitted to the project and a committer familiar with the
> > language accepts them.
> >
> >  - Dennis
> >
> > PS: This does not impact the placing of the current packages
> > into general distribution.  Additional languages can be
> > provided in supplemental distributions.
> >
> > PPS: This is also an area of "Help Wanted" that would be
> > valuable in support of the project.
> 
> I have created a wiki page to coordinate the translations:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=6586657
> 6
> 
> I myself will create the German translation and publish the progress of
> work here:
> https://cwiki.apache.org/confluence/display/OOOUSERS/german+translation
[orcmid] 

Thanks for doing this.  Can you also use a bugzilla issue for submission of the 
text files so they can be verified and used to build additional packages?  

Oh, and to avoid putting .bat files as bugzilla attachments, just add .txt to 
the names.  E.g.,

APPLY-4.2.1-patch1-de.bat.txt

Finally, produce your files in UTF-8, not ISO 8859-1 or any other single-byte 
encoding.

There is a way to change the code page to UTF8 inside a batch script and it 
works so long as cmd.exe is using a font that has the characters.

See the UTF8Check.bat[.txt] file that I have attached.

 - Dennis
> 
> 
> greetings,
> Jörg
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
@echo off
rem UTF8Check.bat 0.0.0   UTF-82016-08-21
rem -1-2-3-4-5-6-7---*

rem ENSURE UTF-8 CHARACTER HANDLING 
FOR /F "tokens=2 delims=:." %%X in ('CHCP') DO SET AOOCP=%%X
remretaining the current code page ID for restoration later
CHCP 65001>NUL
remspecifying UTF-8 for standard display

rem ANNOUNCE THIS SCRIPT
TITLE COMMAND-LINE CONSOLE UTF8 CHECK
COLOR 71
rem   Soft white background with blue text
CLS
ECHO:
ECHO * 0.0.0 UTF8 CONSOLE DISPLAY CHECKING
ECHO:A variety of Unicode character codes are used to display
ECHO:the text, below.  For all of the characters to be presented
ECHO:properly, the font used by the Windows command-line console
ECHO:utility must provide for them.
ECHO:
ECHO:Usually, characters used in your own language will appear
ECHO:correctly.  Some others might not.
ECHO:
ECHO:ASCII abcde xyz   (lower-case Roman characters)
ECHO:Germanäöü ÄÖÜ ß   (accented and special characters)
ECHO:Polishąęźżńł  (accented and special characters)
ECHO:Russian   абвгдеж эюя (cyrillic characters)
ECHO:CJK   你好 (Chinese-Japanese-Korean characters)
ECHO:
ECHO:

rem RESTORE USER'S CODE PAGE
CHCP %AOOCP% >NUL
SET AOOCP=
PAUSE


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

FW: Internationalization of 4.1.2-patch1 (was RE: a question about "APPLY-4.1.2-patch1.bat")

[Dennis E. Hamilton]

This may be of interest to Localization participants.  Please include dev@ list 
in your reply if you are interested.

 - Dennis

> -Original Message-
> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> Sent: Saturday, August 20, 2016 11:26
> To: d...@openoffice.apache.org
> Subject: Internationalization of 4.1.2-patch1 (was RE: a question about
> "APPLY-4.1.2-patch1.bat")
> 
> All of the information on the release of 4.1.2-patch1, including readmes
> and messages from the patch install and uninstall scripts, is in
> English.  See
> <https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/hotfix.html> and the Readme files.  Also, the Windows package
> contains install and uninstall scripts that provide messages in English.
> 
> It would be useful for there to be internationalization of the texts and
> messages, especially for the Windows version.
> 
> If the proportion of languages chosen for downloads is an useful guide,
> 
> English language is selected for over 40% of downloads.
> 
> If French, German, Italian, and Spanish were also supported, then a
> total of 75% of all downloads would be covered.
> 
> To reach 90%, add Japanese, Russian, Polish, Dutch, and Portuguese (BR).
> 
> Supplementing the 4.1.2-patch1 files in this manner is possible, if
> committers are willing to provide translations.  To submit a translation
> for the Windows case, we need a translation of the README and of the
> text messages presented by the APPLY and REVERT scripts in the Zip for
> Windows.  These must be supplied by an OpenOffice committer who can
> provide a PGP signature on their submission, or they must be submitted
> to the project and a committer familiar with the language accepts them.
> 
>  - Dennis
> 
> PS: This does not impact the placing of the current packages into
> general distribution.  Additional languages can be provided in
> supplemental distributions.
> 
> PPS: This is also an area of "Help Wanted" that would be valuable in
> support of the project.
> 
> 
> > -Original Message-
> > From: Jörg Schmidt [mailto:joe...@j-m-schmidt.de]
> > Sent: Saturday, August 20, 2016 01:53
> > To: d...@openoffice.apache.org
> > Subject: a question about "APPLY-4.1.2-patch1.bat"
> >
> > Hello,
> >
> > Maybe, i would like to create a German-annotated version of patch,
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org


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

RE: [Discuss][Wiki]Synchronizing (or not) localized wiki sites [was: Fwd: [UserGuide]My roadmap]

[Dennis E. Hamilton]

@JanI,

Uh oh.

If you don't have explicit agreement from the contributor(s) to a page 
concerning it being offered under a different license, either leave the 
existing license or remove the content.  Those are the only legally-sanitary 
options for works still under copyright.

Declaring a work still in copyright to be orphaned does not give you permission 
to republish it with a different license.  Copyright doesn't work that way, not 
merely in the US.

Secondly, the web site and wiki content were not, as far as I know, included in 
the grant from Oracle. There has clearly been no objection, the domains were 
transferred to the ASF, but technically that does not in any way change the 
copyright status of any of the content.  (The source-code grant, by the way, 
did not transfer any copyright to the ASF.  It simply provided a license to the 
ASF that allowed the ASF to publish and make derivatives under its license.  
Copyright in the original content continues to abide with Oracle.)

While casual treatment of this sort of thing succeeds in some situations, here 
the interests and concerns of The Apache Software Foundation as a 
public-interest entity come into play.  It is expected that folks on Apache 
projects will play nice with the intellectual property of others.  

In particular,

   2) We are allowed to copy  the pages, with changes, and the new page can be
  under a new license

is not ever automatically true.  If there is already a license, the terms of 
that license will determine what is possible with a derivative work (with 
changes).  Even copying is an exclusive right of the copyright holder, so the 
license matters there too.  In the absence of a license, (2) is not permitted 
at all by anyone but the copyright holder or someone authorized by the 
copyright holder (i.e., being licensed to do so).

Finally, and most important, making changes does not give anyone different 
rights to the parts that survive from the original work.  (Fine points about 
license conditions apply here, but one should never assume that a legitimate 
licensing of a derivative work has any impact on the IP interests in the 
surviving content of the original work.)

 - Dennis

-Original Message-
From: janI [mailto:j...@apache.org] 
Sent: Wednesday, June 5, 2013 09:02 AM
To: d...@openoffice.apache.org
Cc: l10n@openoffice.apache.org; d...@openoffice.apache.org
Subject: Re: [Discuss][Wiki]Synchronizing (or not) localized wiki sites [was: 
Fwd: [UserGuide]My roadmap]

[ ... ]
  PDL is a sort of copyleft license.

 This is a excelent question. I ask to my self how the TDF did about
 (more) this question. Can we do like them? Simply overwrite the
 license and to continue the devel? (i remember when they copied all
 sites/docs/contents, like api site, and changed the license)


I have seen similar things happen in other wikis. The way forward seems to
be
1) announce the intention of changing license.
2) request contributors who do not agree, to remove their pages (we have
mail adresses on the users)
3) give contributors time to do it.
4) change license.

We should put the license in as part of create user, as an do you
accept, thereby we only have a  problem with existing users.


  Re-license those pages is not possible without the explicit consent of
 the
  author, and those pages are so old that contact the authors is almost
  impossible. Suppose we update those pages to point to the new material. A
  potential contributor (or just a casual reader) will see the PDL notice
 on
  the portal page, and no notice on the new pages: from the user
 perspective,
  does this means that the new page is also under PDL? We know it isn't,
 but
  this could be a cause of confusion, IMO. So, which is the best way to
 work
  around this problem? Reimplement those pages, making a clear separation
  between new material (under Apache) and legacy content?

 Maybe this is the unique way. By other hand, is a opportunity of
 review all content in the wiki, reorder and clean it, and evolve based
 in the correct license. In some cases, we can see the page history and
 try to find the author. Some parts, i believe that is all from
 Sun/Oracle copyright, so transfered to ASF.


A cleanup would be nice independent of which way we go

The word re-licensing is not a show stopper.
1) We are not obligated to store those pages for ever, we can, with notice,
delete the pages
2) We are allowed to copy  the pages, with changes, and the new page can be
under a new license

rgds
jan I


 My 2¢
 Claudio

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




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