[ 
https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468077
 ] 

Halley Pacheco de Oliveira commented on DERBY-2237:
---------------------------------------------------

Jean,

If we remove the line:

Segunda Edição (Julho de 2005)

and change the line:

Copyright 1997, 2005 Apache Software Foundation, ou seus concessores de 
licença, conforme se aplique.

to:

Copyright 2004, 2006 The Apache Software Foundation

the text that is already committed will match the text shown in

http://www.apache.org/licenses/LICENSE-2.0.html#apply

translated into Brazilian Portuguese

> Cleanup copyrights in the DITA source and generated docs
> --------------------------------------------------------
>
>                 Key: DERBY-2237
>                 URL: https://issues.apache.org/jira/browse/DERBY-2237
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.2.1.6, 10.2.2.0
>         Environment: linux
>            Reporter: scott hutinger
>            Priority: Blocker
>         Attachments: dita2fo-shell-copyr1.diff.gz, pt_BR_copyright.diff, 
> pt_BR_copyright.diff.html, radmincopyright.html, rgscopyright.html, 
> rrefcopyright.html
>
>
> Problems include:
> 1) The PDF docs currently include an empty "Copyright" string in the header. 
> dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright 
> header which is currently blank.  This is from march 9, 2006.
> 2) Some source files have the old style copyright in the header that is not 
> in compliance with http://www.apache.org/legal/src-headers.html. For example, 
> see src/ref/rrefsistabssyscolperms.dita
> 3) The generated html docs have new copyright tags added, such as these 
> entries in ref/crefjavbclobnot.html
> <meta name="copyright" content="(C) Copyright 2005" />
> <meta name="DC.rights.owner" content="(C) Copyright 2005" />

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to