4.0.1_release_blocker granted: [Bug 123003] Text invisible while editing in particular old documents

[bugzilla]

j...@apache.org has granted Armin Le Grand 's request for
4.0.1_release_blocker:
Bug 123003: Text invisible while editing in particular old documents
https://issues.apache.org/ooo/show_bug.cgi?id=123003


--- Additional Comments from j...@apache.org
approve showstopper request

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

4.0.1_release_blocker denied: [Bug 123014] Generate new kid (KeyID) localize.sdf file

[bugzilla]

j...@apache.org has denied Andrea Pescetti 's request for
4.0.1_release_blocker:
Bug 123014: Generate new kid (KeyID) localize.sdf file
https://issues.apache.org/ooo/show_bug.cgi?id=123014


--- Additional Comments from j...@apache.org
I don't think this is a showstopper. We should first figure out how exactly it
works and should be used to produce a usable result. And this work should
continue on trunk

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

A finding and a further question about 122840

[Clarence GUO]

HI~
I have a finding on 122840 and have a code can fix it. But I have a further
question about technique detail on this issue. Don't know if anybody is
familiar with.

In 120478, zhaoshzh added support for scope of name range. MS Excel
can define a same name to a range on different sheets. For example
defines "MyRange" to "Sheet1.A1:A4" with scope in sheet1 and defines
"MyRange" again to "Sheet2.A1:A4" with scope in sheet2.
In order to add this support, he changed code in ScXMLImport::SetNamedRanges(),
from
xNamedRanges->addNewByName((*aItr)->sName, sTempContent, aCellAddress,
GetRangeType((*aItr)->sRangeType));
to
xNamedRanges->addNewByScopeName( sTabName, (*aItr)->sName,
(*aItr)->sContent, aCellAddress, GetRangeType((*aItr)->sRangeType) );
addNewByScopeName is a new method, the difference with addNewByName is
it added a new parameter sTabName in order to distinguish the scope.
Others are same. But note he also changed the third parameter of the
new method. In the old method, that parameter is sTempContent, it is
string "0". However, in the new method he passed (*aItr)->sContent
into, (*aItr)->sContent is the real content of the name. For example,
for above illustration, "Sheet1.A1:A4" is the content of range name
"MyRange".
I'm not sure whether it is his pen mistake, but from logic, as he only
add a new parameter for scope identification, the old parameters
should not be changed. So I just change (*aItr)->sContent back to
sTempContent, then it works.
And there's no problem on 120478 sample file with the fix. I did some
test, haven't find problem.
But I don't know why we need to pass a "0" string as content into the
method. Why not the real content?
Does anybody know that?

Thanks
Clarence

Re: 4.0.1_release_blocker denied: [Bug 123014] Generate new kid (KeyID) localize.sdf file

[Andrea Pescetti]

bugzi...@apache.org wrote:

--- Additional Comments from j...@apache.org
I don't think this is a showstopper. We should first figure out how exactly it
works and should be used to produce a usable result. And this work should
continue on trunk


I don't really get this. It works on trunk, I even posted screenshots to 
the l10n list. What is still missing?


It is not a product release blocker, but it is a "community" release 
blocker: volunteers need a KeyID build to work effectively, and we 
already had requests from 3 language teams; but Herbert won't create 
(via buildbots) KeyID builds until the AOO401 branch has an updated 
localize.sdf for "kid"; that file has been in trunk since yesterday and 
must just be copied to AOO401; the only way to copy something to AOO401 
is to ask that it is a release blocker... so this seems the only process 
to me.


Of course, I can perfectly live with my personal kid build, but this 
won't make life easier for other volunteers.


Regards,
  Andrea.

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

4.0.1_release_blocker requested: [Bug 123129] Anchor line for comments is too fine for viewing

[bugzilla]

Armin Le Grand  has asked  for 4.0.1_release_blocker:
Bug 123129: Anchor line for comments is too fine for viewing
https://issues.apache.org/ooo/show_bug.cgi?id=123129


--- Additional Comments from Armin Le Grand 
ALG: Changed and experimented to get to a discrete LineWidth of 1.6 (pixels),
looks good on Win and Linux and as in 3.4.1, too. Preparing checkin, requesting
ReleaseBlocker flag for AOO3.4.1

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

Recommended way to merge commits to AOO401?

[Andrea Pescetti]

What is the recommended way to merge commits to AOO401? As I see it, the 
textbook steps would be to cherry-pick them from trunk, so:


1) Commit fix to trunk as revision N (in my case, 1518832, affecting 
main/extensions.lst)


2) Chdir to an AOO401 checkout

3) Check the diff to be applied with something like

main$ svn diff -c 1518832 
https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst


4) Merge the commit by cherry-picking, with something like

main$ svn merge -c 1518832 
https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst


Is this the recommended way? Or are showstoppers supposed to be fixed on 
AOO401 first and be ported to trunk later, maybe with a single merge 
operation? If there are some conventions, I'll apply them for the fixes 
I'll commit during the weekend.


Regards,
  Andrea.

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

Re: Recommended way to merge commits to AOO401?

[Jürgen Schmidt]

On 8/30/13 1:23 PM, Andrea Pescetti wrote:
> What is the recommended way to merge commits to AOO401? As I see it, the
> textbook steps would be to cherry-pick them from trunk, so:
> 
> 1) Commit fix to trunk as revision N (in my case, 1518832, affecting
> main/extensions.lst)
> 
> 2) Chdir to an AOO401 checkout
> 
> 3) Check the diff to be applied with something like
> 
> main$ svn diff -c 1518832
> https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst
> 
> 4) Merge the commit by cherry-picking, with something like
> 
> main$ svn merge -c 1518832
> https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst
> 
> Is this the recommended way? Or are showstoppers supposed to be fixed on
> AOO401 first and be ported to trunk later, maybe with a single merge
> operation? If there are some conventions, I'll apply them for the fixes
> I'll commit during the weekend.

important is that the fix is available on both. I fix it on the branch
first and merge it on trunk. Others do it exactly in the way you did.

But in general I think it make sense if the developer takes care of
making the fix available where needed.


If we have a bigger range of changes made on a branch and changes made
in parallel on trunk merging it in one step can be trigger many
conflicts. But I am open for everything

Juergen


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


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

Re: Recommended way to merge commits to AOO401?

[Armin Le Grand]

Hi Andrea,

On 30.08.2013 13:23, Andrea Pescetti wrote:
What is the recommended way to merge commits to AOO401? As I see it, 
the textbook steps would be to cherry-pick them from trunk, so:


1) Commit fix to trunk as revision N (in my case, 1518832, affecting 
main/extensions.lst)


2) Chdir to an AOO401 checkout

3) Check the diff to be applied with something like

main$ svn diff -c 1518832 
https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst


4) Merge the commit by cherry-picking, with something like

main$ svn merge -c 1518832 
https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst


Is this the recommended way? Or are showstoppers supposed to be fixed 
on AOO401 first and be ported to trunk later, maybe with a single 
merge operation? If there are some conventions, I'll apply them for 
the fixes I'll commit during the weekend.


I do it exactly that way round, main reason is that I can only give an 
evaluation if the fix is save to go to AOO401 if I have done it, so I 
first do it on trunk where it is needed in any case. If it's safe to get 
to AOO401, I then merge it there.


HTH!


Regards,
  Andrea.

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


--
ALG

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

4.0.1_release_blocker granted: [Bug 123129] Anchor line for comments is too fine for viewing

[bugzilla]

j...@apache.org has granted Armin Le Grand 's request for
4.0.1_release_blocker:
Bug 123129: Anchor line for comments is too fine for viewing
https://issues.apache.org/ooo/show_bug.cgi?id=123129


--- Additional Comments from j...@apache.org
approve showstopper request

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

Re: Recommended way to merge commits to AOO401?

[Jürgen Schmidt]

On 8/30/13 1:52 PM, Armin Le Grand wrote:
> Hi Andrea,
> 
> On 30.08.2013 13:23, Andrea Pescetti wrote:
>> What is the recommended way to merge commits to AOO401? As I see it,
>> the textbook steps would be to cherry-pick them from trunk, so:
>>
>> 1) Commit fix to trunk as revision N (in my case, 1518832, affecting
>> main/extensions.lst)
>>
>> 2) Chdir to an AOO401 checkout
>>
>> 3) Check the diff to be applied with something like
>>
>> main$ svn diff -c 1518832
>> https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst
>>
>> 4) Merge the commit by cherry-picking, with something like
>>
>> main$ svn merge -c 1518832
>> https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst
>>
>> Is this the recommended way? Or are showstoppers supposed to be fixed
>> on AOO401 first and be ported to trunk later, maybe with a single
>> merge operation? If there are some conventions, I'll apply them for
>> the fixes I'll commit during the weekend.
> 
> I do it exactly that way round, main reason is that I can only give an
> evaluation if the fix is save to go to AOO401 if I have done it, so I
> first do it on trunk where it is needed in any case. If it's safe to get
> to AOO401, I then merge it there.

ok I see most others including you  fix it first on trunk and then merge
it on the branch. I will adapt this way in the future ;-)

Juergen

> 
> HTH!
>>
>> Regards,
>>   Andrea.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
> -- 
> ALG
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


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

Re: Recommended way to merge commits to AOO401?

[Oliver-Rainer Wittmann]

Hi,

On 30.08.2013 13:23, Andrea Pescetti wrote:

What is the recommended way to merge commits to AOO401? As I see it, the
textbook steps would be to cherry-pick them from trunk, so:

1) Commit fix to trunk as revision N (in my case, 1518832, affecting
main/extensions.lst)

2) Chdir to an AOO401 checkout

3) Check the diff to be applied with something like

main$ svn diff -c 1518832
https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst

4) Merge the commit by cherry-picking, with something like

main$ svn merge -c 1518832
https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst

Is this the recommended way? Or are showstoppers supposed to be fixed on
AOO401 first and be ported to trunk later, maybe with a single merge
operation? If there are some conventions, I'll apply them for the fixes
I'll commit during the weekend.



For me that is the _recommended_ way.
Keep in mind that it is an recommendation, there might and will be 
exceptions, I think.


Best regards, Oliver.

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

Re: Recommended way to merge commits to AOO401?

[Herbert Duerr]

On 30.08.2013 13:52, Armin Le Grand wrote:

 Hi Andrea,

On 30.08.2013 13:23, Andrea Pescetti wrote:

What is the recommended way to merge commits to AOO401? As I see it,
the textbook steps would be to cherry-pick them from trunk, so:

1) Commit fix to trunk as revision N (in my case, 1518832, affecting
main/extensions.lst)

2) Chdir to an AOO401 checkout

3) Check the diff to be applied with something like

main$ svn diff -c 1518832
https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst

4) Merge the commit by cherry-picking, with something like

main$ svn merge -c 1518832
https://svn.apache.org/repos/asf/openoffice/trunk/main/extensions.lst

Is this the recommended way? Or are showstoppers supposed to be fixed
on AOO401 first and be ported to trunk later, maybe with a single
merge operation? If there are some conventions, I'll apply them for
the fixes I'll commit during the weekend.


I do it exactly that way round, main reason is that I can only give an
evaluation if the fix is save to go to AOO401 if I have done it, so I
first do it on trunk where it is needed in any case. If it's safe to get
to AOO401, I then merge it there.


I agree, first commit to trunk then cherry-pick into the release branch 
is the right way.


I'm also quite sure that using only one direction helps subversion to 
track the mergeinfos better. Regarding mergeinfos I learned in [1] that 
there were problems in subversion<=1.6 so that a lot of unrelated 
mergeinfos were committed. Even in infrastructures like XCode that come 
with svn 1.6 the upgrade to svn 1.7 is worth the trouble.


[1] https://issues.apache.org/ooo/show_bug.cgi?id=122829#c11

As I requested in [2] using git would have some benefits too, but that 
issue got closed. We need consensus first whether we want to have a 
read-only git-mirror of our svn repository or to whether we want to 
fully switch to git (read-write).


[2] https://issues.apache.org/jira/browse/INFRA-5590

Herbert

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

Re: template troubles in "xx" pseudo NL website

[Rob Weir]

On Thu, Aug 29, 2013 at 1:08 PM, Ariel Constenla-Haile
 wrote:
> On Thu, Aug 29, 2013 at 09:49:33AM -0400, Rob Weir wrote:
>> As I mentioned earlier I'm trying to make a self-contained English
>> language website that can copied and translated to make new (or
>> refreshed) NL websites.  This includes the 25 or so core pages that
>> should be translated for every language.
>>
>> You can see the site here in:
>>
>> https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/xx/
>>
>> or a live copy here:
>>
>> http://www.openoffice.org/xx/
>>
>> As you can see, it is not picking up the topnav at all.  Ditto for the
>> side navigation on pages like:
>>
>> http://www.openoffice.org/xx/why/
>>
>> Any idea what I'm missing?  I've added a ssi.mdtext file into the
>> templates directory, e.g.,:
>>
>> https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/templates/xx/ssi.mdtext
>
> I applied the general changes to make the /xx/ site work. It had some
> issues, among those mixed line endings. There are still some things to fix
> (specially with links). In general, you should look at the /es/ site to
> see how it should be done; there I tried to avoid relative (of the kind
> ../) and fixed (contenting http://www.openoffice.org/...) links, and use
> the path to the site, for example:
>
> 
> 
>
> @import url(/support/print.css);
>
> this is less error-prone.
>

Thanks.  I'll take a deeper look.

But one question:  what is the strategy on locale detection on the
download page for NL pages?  It looks like you are hardcoding it to
"es", but preserving the OS detection code?

I see:

var NL_LANGUAGE = "es";

Is that all that is needed?  We can otherwise just reuse the same scripts?

-Rob

>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina

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

Re: IBM Connections Connector for Apache OpenOffice

[Jörg Schmidt]

Hello, 

> From: Rob Weir [mailto:robw...@apache.org] 

> So what does this mean?

Thanks for the information.

> 1.  We're *not* promoting a separate version of OpenOffice.  There is
> no "IBM Edition" or "IBM OpenOffice".  Historically, these things,
> whether Novell Edition, or Oracle Open Office, have created conflicts
> and tensions.  

well, tensions were probably other causes.

I and some of my clients (You know I offering professional support for 
OpenOffice), regret that there is no specific AOO version for business user.

It is true that Sun had problems to assert itself with StarOffice in the 
market, but IBM could do better.

It is a sovereign decision by IBM that does not want to, but I'm afraid it is 
not an optimal decision. In any case, it was not a good signal to the market 
only to publish this document:
http://oakmont.co.uk/Download/Symphony%20Apache%20Future%20FAQ%2002-2012.pdf

and now to see otherwise. Sorry, but that's my opinion.

> Our goal is to make the version of AOO that anyone can
> download from the www.openoffice.org stable enough for anyone,
> including our customers, to run.  

In my opinion it is wrong to assume that a distribution of AOO would (whether 
from IBM or other) directed against the interests of AOO itself.


That's just my opinion, I would not discuss it.


Greetings,
Jörg


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

Re: IBM Connections Connector for Apache OpenOffice

[Rob Weir]

On Fri, Aug 30, 2013 at 8:27 AM, Jörg Schmidt  wrote:
> Hello,
>
>> From: Rob Weir [mailto:robw...@apache.org]
>
>> So what does this mean?
>
> Thanks for the information.
>
>> 1.  We're *not* promoting a separate version of OpenOffice.  There is
>> no "IBM Edition" or "IBM OpenOffice".  Historically, these things,
>> whether Novell Edition, or Oracle Open Office, have created conflicts
>> and tensions.
>
> well, tensions were probably other causes.
>
> I and some of my clients (You know I offering professional support for 
> OpenOffice), regret that there is no specific AOO version for business user.
>

How would a "business" version of AOO differ from the version that we
release from Apache?  How would the code be different?

> It is true that Sun had problems to assert itself with StarOffice in the 
> market, but IBM could do better.
>

I believe we can do better as well, by not repeating the same mistakes.

> It is a sovereign decision by IBM that does not want to, but I'm afraid it is 
> not an optimal decision. In any case, it was not a good signal to the market 
> only to publish this document:
> http://oakmont.co.uk/Download/Symphony%20Apache%20Future%20FAQ%2002-2012.pdf
>
> and now to see otherwise. Sorry, but that's my opinion.
>

I believe what we're doing now is superior to what was talked about
two years ago.  Much has happened since then, including graduation and
successful releases.  It is clear to me that professional quality code
can be developed and delivered from within the project.

>> Our goal is to make the version of AOO that anyone can
>> download from the www.openoffice.org stable enough for anyone,
>> including our customers, to run.
>
> In my opinion it is wrong to assume that a distribution of AOO would (whether 
> from IBM or other) directed against the interests of AOO itself.
>

The issue is not packaging.  The issue is the implicit forking that
comes from having an "IBM Edition" versus a "Community edition".
Remember, that was essentially the approach used by Symphony.  There
is a lot of overhead in such an approach, as well as the tensions it
raises in the community.  I realize this may be the business model of
some Linux vendors.  "If you want quality you need to pay for it", I
remember one LO developer saying.  But this doesn't feel like a good
fit for OpenOffice.

And remember, we're making good use of extensions, which are specific
to IBM products.  I don't see any reason why the core code in AOO
needs to be different for business users.  The bug fixes and features
they want are ones that anyone would want.  So if it makes it easier,
think of IBM Edition = AOO + IBM Extensions.  But it makes no sense to
offer that as an individual package, since our customers almost all
want custom deployment support.  We're not selling individual shrink
wrapped licenses to consumers.

Regards,

-Rob

>
> That's just my opinion, I would not discuss it.
>
>
> Greetings,
> Jörg
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

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

RE: Bug 121014 - Fidelity issues

[V Stuart Foote]

Do you like a title of "Fidelity issues - incorrect rendering of ODF or MS 
formats" for the task?


From: Rainer Bielefeld 
Sent: Thursday, August 29, 2013 11:25 PM
To: q...@openoffice.apache.org
Cc: dev@openoffice.apache.org >> "dev@openoffice.apache.org"
Subject: Bug 121014 - Fidelity issues

Hi all,

can someone please leve a comment in above mentioned bug and explain
what "Fidelity issues" are?

Thank you


Rainer

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




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

4.0.1_release_blocker requested: [Bug 122982] Copying spreadsheet into another document in bit map format has disappeared in Version 4. Worked on Version 3.

[bugzilla]

Armin Le Grand  has asked  for 4.0.1_release_blocker:
Bug 122982: Copying spreadsheet into another document in bit map format has
disappeared in Version 4.  Worked on Version 3.
https://issues.apache.org/ooo/show_bug.cgi?id=122982


--- Additional Comments from Armin Le Grand 
ALG: Okay, looks good and is plausible. Also a candidate for AOO401, setting
flag. Comitted to trunk.

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

[RELEASE]: new snapshot build for AOO 4.0.1

[Jürgen Schmidt]

Hi,

we have prepared a new snapshot build for AOO 4.0.1 for Windows, MacOS
and Linux based on the SNAPSHOT tag.

The SNAPSHOT tag rev. 1518670 is based on revision 1518667 on branch AOO401

We have started to provide Linux builds to start early testing of our
builds and ensure that they can be used as replacement for Ariels
builds. We build also on CentOS5 systems that should have the baseline.

Ariel pointed out that he won't be able to deliver the builds in the
future starting with the beginning of September. At this point I would
like to thank you Ariel for his support in the past. I know what it
means to do the builds, sign and upload it.

The wiki page is updated and for Linux you can find archive builds as
well directly in the directory (not linked via the wiki).

The differences between this and the last snapshot can be found under
http://people.apache.org/~jsc/developer-snapshots/snapshot/izlist.htm

Please note that the translation updates are not yet marked as fixed. I
have taken a snapshot from Pootle to support early testing. Please add
comments in the issue or mark it as fixed if no further updates via
Pootle can be expected. It will help to reduce the workload on my side.

Updated languages are: sk, nl, en-GB, es, km, pl, zh-TW, pt

NOTE: the upload is ongoing, if a link is not yet working try it later.
I will be offline until Monday ...


Thanks

Juergen

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

Fw: open office vers 4

[Antonio De Rosa]

- Original Message - 
From: Antonio De Rosa 
To: dev@openoffice.apache.org ; us...@openoffice.apache.org 
Sent: Thursday, August 29, 2013 4:24 PM
Subject: open office vers 4


Buongiorno
sono alcuni anni che adopero openoffice ed ho sempre scaricato  le nuove 
versioni.
Vi devo segnalare che la versione 4 ha rallentato molto le funzionalità di 
salvataggio e caricamento dati.
E'  molto lento nell'apertura e  non visualizza bene le schede excel calc.
E' lentissimo nel salvataggio quando i file sono rilevanti e con molte pagine.  
 
Avrei quasi voglia di tornare alla versione precedente.
FATE QUALCOSA.
saluti   
antonioderosa
Napoli

Re: KEYS

[Rob Weir]

Moving conversation over to the dev list...

On Sun, Aug 25, 2013 at 8:18 PM, Ariel Constenla-Haile
 wrote:
> On Sun, Aug 25, 2013 at 05:31:35PM -0400, Rob Weir wrote:
>> > I wanted to verify the
>> > Apache_OpenOffice_4.0.0_Linux_x86-64_install-rpm_en-US.tar.gz.asc
>> > against my download.  I downloaded the KEYS using: wget
>> > http://www.apache.org/dist/openoffice/KEYS Then I imported the keys.
>> >
>> > But when I ran gpg --verify it said:
>> >
>> > $ gpg --verify
>> > Apache_OpenOffice_4.0.0_Linux_x86-64_install-rpm_en-US.tar.gz.asc
>> > gpg: Signature made Tue 16 Jul 2013 05:39:05 PM CDT using RSA
>> > key ID B8E50356 gpg: Can't check signature: No public key
>> >
>> > The Key ID B8E50356 is not in the set I downloaded from your KEYS
>> > file.  Why is it not in there??
>> >
>>
>> Hi Ariel,  is B8E50356 your key?
>
> Yes, it is a bug that my key is not in
> http://www.apache.org/dist/openoffice/KEYS
>
> This file should be a copy of
> https://people.apache.org/keys/group/openoffice.asc or
> https://people.apache.org/keys/group/openoffice-pmc.asc (in case only
> PMC members are supposed to sign artifacts).
>

Does anyone know:  can we (may we?) do this now?  Or is this something
to fix in 4.0.1 release?

-Rob


>
> @OP: please import the keys from
> https://people.apache.org/keys/group/openoffice-pmc.asc
>
>> > Allen -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14
>> > (GNU/Linux)
>> >
>> > iQEcBAEBAgAGBQJSGABoAAoJEK3AFbtYOknnVI0IALxbJlIW58Ll3R8aryWQXX4k
>> > GJ1+Gh5cWFDYvFq9Cetz86vnxDuCaiVMxEOwnRc+PtBQHWHpzRuSKTG16fOs/5JD
>> > SGykhVkgdkRodpiuQKE8n/kV8+/aEaa+9WpxVdn+eqhTsi3nc570JQbOaw0sCOrY
>> > Nrdwm5Urm7w6wcP240g5UD4pjfXqAieEEe/0FdJQepikt7VFlRjsvRYVekSDHkUL
>> > t5XgL3LQAaTt47vMM9EyPMxK2RfIG2dXUQ54phtgFs9CUt2yqVF4s8mA2Ha+moPu
>> > rc2mS4vrKeswCO6ywyfDtaQnbaZrLxPG0y9Ql0hcUv5CEHE0eRxnJgkkTYzVUaI=
>> > =0QtH -END PGP SIGNATURE-
>
> I suggest you configure Enigmail in Thunderbird to sign using PGP/MIME
> instead of the old-fashioned inline-PGP, in Thunderbird's Account
> Settings go to OpenPGP Options and enable "Use PGP/MIME by default", as
> explained here http://www.rainydayz.org/content/81-account-settings
>
>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina

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

Re: IBM Connections Connector for Apache OpenOffice

[Jörg Schmidt]

> From: Rob Weir [mailto:robw...@apache.org] 

> > I and some of my clients (You know I offering professional 
> support for OpenOffice), regret that there is no specific AOO 
> version for business user.
> >
> 
> How would a "business" version of AOO differ from the version that we
> release from Apache?  How would the code be different?

The code does not have to be different (he was in StarOffice not), but it is 
about confidence in the market. For example, IBM could provide product warranty 
for its own distribution.

> I believe what we're doing now is superior to what was talked about
> two years ago.  Much has happened since then, including graduation and
> successful releases.  It is clear to me that professional quality code
> can be developed and delivered from within the project.
> 
> >> Our goal is to make the version of AOO that anyone can
> >> download from the www.openoffice.org stable enough for anyone,
> >> including our customers, to run.
> >
> > In my opinion it is wrong to assume that a distribution of 
> AOO would (whether from IBM or other) directed against the 
> interests of AOO itself.
> >
> 
> The issue is not packaging.  The issue is the implicit forking that
> comes from having an "IBM Edition" versus a "Community edition".
> Remember, that was essentially the approach used by Symphony.  There
> is a lot of overhead in such an approach, as well as the tensions it
> raises in the community.  I realize this may be the business model of
> some Linux vendors.  "If you want quality you need to pay for it", I
> remember one LO developer saying.  But this doesn't feel like a good
> fit for OpenOffice.
> 
> And remember, we're making good use of extensions, which are specific
> to IBM products.  I don't see any reason why the core code in AOO
> needs to be different for business users.  The bug fixes and features
> they want are ones that anyone would want.  So if it makes it easier,
> think of IBM Edition = AOO + IBM Extensions.  But it makes no sense to
> offer that as an individual package, since our customers almost all
> want custom deployment support.  We're not selling individual shrink
> wrapped licenses to consumers.

I respect your arguments, only my opinion is an other. IBM does not use a 
chance here.


Greetings,
Jörg


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

Re: template troubles in "xx" pseudo NL website

[Ariel Constenla-Haile]

On Fri, Aug 30, 2013 at 08:26:51AM -0400, Rob Weir wrote:
> But one question:  what is the strategy on locale detection on the
> download page for NL pages?  It looks like you are hardcoding it to
> "es", but preserving the OS detection code?
> 
> I see:
> 
> var NL_LANGUAGE = "es";
> 
> Is that all that is needed?  We can otherwise just reuse the same scripts?

yes, var NL_LANGUAGE = ""; will default to en-US.

The download page, with all that javascript in it, is rather hard to
translate. Isn't it possible to use a cgi script (server-side vs.
client-side js)?


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpaPlg_jcJ6D.pgp
Description: PGP signature

Re: A finding and a further question about 122840

[Oliver-Rainer Wittmann]

Hi,

On 30.08.2013 11:21, Clarence GUO wrote:

HI~
I have a finding on 122840 and have a code can fix it. But I have a further
question about technique detail on this issue. Don't know if anybody is
familiar with.

In 120478, zhaoshzh added support for scope of name range. MS Excel
can define a same name to a range on different sheets. For example
defines "MyRange" to "Sheet1.A1:A4" with scope in sheet1 and defines
"MyRange" again to "Sheet2.A1:A4" with scope in sheet2.
In order to add this support, he changed code in ScXMLImport::SetNamedRanges(),
from
xNamedRanges->addNewByName((*aItr)->sName, sTempContent, aCellAddress,
GetRangeType((*aItr)->sRangeType));
to
xNamedRanges->addNewByScopeName( sTabName, (*aItr)->sName,
(*aItr)->sContent, aCellAddress, GetRangeType((*aItr)->sRangeType) );
addNewByScopeName is a new method, the difference with addNewByName is
it added a new parameter sTabName in order to distinguish the scope.
Others are same. But note he also changed the third parameter of the
new method. In the old method, that parameter is sTempContent, it is
string "0". However, in the new method he passed (*aItr)->sContent
into, (*aItr)->sContent is the real content of the name. For example,
for above illustration, "Sheet1.A1:A4" is the content of range name
"MyRange".
I'm not sure whether it is his pen mistake, but from logic, as he only
add a new parameter for scope identification, the old parameters
should not be changed. So I just change (*aItr)->sContent back to
sTempContent, then it works.
And there's no problem on 120478 sample file with the fix. I did some
test, haven't find problem.
But I don't know why we need to pass a "0" string as content into the
method. Why not the real content?
Does anybody know that?



I think you find the defect cause and also the solution.
Further details and discussion directly in the issue.

Best regards, Oliver.

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

Re: template troubles in "xx" pseudo NL website

[sebb]

On 30 August 2013 15:28, Ariel Constenla-Haile  wrote:
> On Fri, Aug 30, 2013 at 08:26:51AM -0400, Rob Weir wrote:
>> But one question:  what is the strategy on locale detection on the
>> download page for NL pages?  It looks like you are hardcoding it to
>> "es", but preserving the OS detection code?
>>
>> I see:
>>
>> var NL_LANGUAGE = "es";
>>
>> Is that all that is needed?  We can otherwise just reuse the same scripts?
>
> yes, var NL_LANGUAGE = ""; will default to en-US.
>
> The download page, with all that javascript in it, is rather hard to
> translate. Isn't it possible to use a cgi script (server-side vs.
> client-side js)?

If the ASF servers can support server-side processing then it should
be possible to use that for the OS auto-detection as well.

However, if client-side processing is required, maybe the NL text
strings should be extracted into a JSON object, making the javascript
generic.
That would make it much easier to maintain - only a single copy.

Failing that, it should be fairly simple (?) to extract the NL strings
into JS variables and group them at the start of the page.

>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina

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

4.0.1_release_blocker requested: [Bug 122840] Ranged names don't work anymore

[bugzilla]

Oliver-Rainer Wittmann  has asked  for 4.0.1_release_blocker:
Bug 122840: Ranged names don't work anymore
https://issues.apache.org/ooo/show_bug.cgi?id=122840


--- Additional Comments from Oliver-Rainer Wittmann 
fix available

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

Re: template troubles in "xx" pseudo NL website

[Rob Weir]

On Fri, Aug 30, 2013 at 10:28 AM, Ariel Constenla-Haile
 wrote:
> On Fri, Aug 30, 2013 at 08:26:51AM -0400, Rob Weir wrote:
>> But one question:  what is the strategy on locale detection on the
>> download page for NL pages?  It looks like you are hardcoding it to
>> "es", but preserving the OS detection code?
>>
>> I see:
>>
>> var NL_LANGUAGE = "es";
>>
>> Is that all that is needed?  We can otherwise just reuse the same scripts?
>
> yes, var NL_LANGUAGE = ""; will default to en-US.
>
> The download page, with all that javascript in it, is rather hard to
> translate. Isn't it possible to use a cgi script (server-side vs.
> client-side js)?
>

I assume you mean JS like this that generates the UI for the download box:

if ( LINK.toLowerCase().indexOf( "sourceforge" ) != -1 ) {
  // Download directly from a mirror with displayed platform and language.
  document.write( "" );
  document.write( "Download
Apache OpenOffice " + VERSION + ""
  + "Click here for the most recent
version for:"
  + "" + UI_PLATFORM + " and " + LANG_ARRAY[ 2 ] + "
(~" + FILESIZE + " MByte)" );


That is a mix of HTML structure, code and language strings.  I wonder
if we could define a per-locale strings with place holders like we do
with Pootle:

"Download Apache OpenOffice %s"
"Click here for the most recent version for:"
"%s and %s (%s Megabytes)"

If we get that kind of separation, then doing the substitutions could
be done server side or client side.

-Rob


>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina

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

Re: [RELEASE]: new snapshot build for AOO 4.0.1

[Larry Gusaas]

I clicked on the link to download the en-GB language pack. It downloaded the full version 
instead. It seems the other language packs would do the same.


On 2013-08-30 7:27 AM Jürgen Schmidt wrote:

we have prepared a new snapshot build for AOO 4.0.1 for Windows, MacOS
and Linux based on the SNAPSHOT tag.

The SNAPSHOT tag rev. 1518670 is based on revision 1518667 on branch AOO401



--
_

Larry I. Gusaas
Moose Jaw, Saskatchewan Canada
Website: http://larry-gusaas.com
"An artist is never ahead of his time but most people are far behind theirs." - 
Edgard Varese




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

Bugzilla Index

[Rory O'Farrell]

Is the Bugzilla index up to date? I've tried a few searches for words in 123129 
subject with no success. It would find the 123129 issue, given the number, but 
not using any of the subject words. acknak (on en-Forum) found similarly.

-- 
Rory O'Farrell 

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

Translation integration

[Michal Hriň]

Hi,

I am planning this weekend to play with .sdf files.
(converting, merging, etc.)

I found some links on wiki [1],[2].

Is this information still relevant ?
There are mentioned tool "gsicheck [3]", which Juergen mention early too.
Where can I download this tool ?

[1] http://wiki.openoffice.org/wiki/Localization_for_developers
[2] http://wiki.openoffice.org/wiki/Translation:General_Information
[3] http://wiki.openoffice.org/wiki/Gsicheck

Regards,
Michal Hriň

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

Re: IBM Connections Connector for Apache OpenOffice

[Rob Weir]

On Fri, Aug 30, 2013 at 10:06 AM, Jörg Schmidt  wrote:
>> From: Rob Weir [mailto:robw...@apache.org]
>
>> > I and some of my clients (You know I offering professional
>> support for OpenOffice), regret that there is no specific AOO
>> version for business user.
>> >
>>
>> How would a "business" version of AOO differ from the version that we
>> release from Apache?  How would the code be different?
>
> The code does not have to be different (he was in StarOffice not), but it is 
> about confidence in the market. For example, IBM could provide product 
> warranty for its own distribution.
>

OK.  Maybe you misunderstood me then.  I'm not saying that we don't
sell services and support related to AOO.  We do.  But we don't
package and distribute a separate version of AOO.

Regards,

-Rob


>> I believe what we're doing now is superior to what was talked about
>> two years ago.  Much has happened since then, including graduation and
>> successful releases.  It is clear to me that professional quality code
>> can be developed and delivered from within the project.
>>
>> >> Our goal is to make the version of AOO that anyone can
>> >> download from the www.openoffice.org stable enough for anyone,
>> >> including our customers, to run.
>> >
>> > In my opinion it is wrong to assume that a distribution of
>> AOO would (whether from IBM or other) directed against the
>> interests of AOO itself.
>> >
>>
>> The issue is not packaging.  The issue is the implicit forking that
>> comes from having an "IBM Edition" versus a "Community edition".
>> Remember, that was essentially the approach used by Symphony.  There
>> is a lot of overhead in such an approach, as well as the tensions it
>> raises in the community.  I realize this may be the business model of
>> some Linux vendors.  "If you want quality you need to pay for it", I
>> remember one LO developer saying.  But this doesn't feel like a good
>> fit for OpenOffice.
>>
>> And remember, we're making good use of extensions, which are specific
>> to IBM products.  I don't see any reason why the core code in AOO
>> needs to be different for business users.  The bug fixes and features
>> they want are ones that anyone would want.  So if it makes it easier,
>> think of IBM Edition = AOO + IBM Extensions.  But it makes no sense to
>> offer that as an individual package, since our customers almost all
>> want custom deployment support.  We're not selling individual shrink
>> wrapped licenses to consumers.
>
> I respect your arguments, only my opinion is an other. IBM does not use a 
> chance here.
>
>
> Greetings,
> Jörg
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

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

Re: Where can I find the new logo (svg) usable in AOO

[Drew Jensen]

Hi Guys,

On this issue - I believe the (one of) problem is they way superscript is
being handled - it breaks the text after any superscript. Of course the
browser code is a factor also - I have some examples of SVG outputs from
AOO4 and different browsers, really the only browser that consistently
renders the file the way it was intended to be seen is Opera, Firefox is
next closest and Google..'also ran' - but the one thing that seems to
really be broken is handling superscript characters.

//drew


On Fri, Aug 23, 2013 at 3:08 PM, Andrea Pescetti wrote:

> On 22/08/2013 Jürgen Schmidt wrote:
>
>> On 8/21/13 9:54 PM, Andrea Pescetti wrote:
>>
>>> Discussed here last month. Alexandro wrote it's due to the font:
>>> http://markmail.org/message/**u5pbe2jkrvnw3vdl
>>>
>> the explanation don't explain why it works well in gimp or Inkscape. But
>> anyway I will ask Armin what the problem really is when he will be back.
>>
>
> OK, and then it would be great to make a reference SVG version of the
> logo, to be stored under /branding, that opens correctly in OpenOffice and
> other programs... If the one with embedded fonts has some special
> advantages it can stay, but the reference version should be as compatible
> as possible.
>
>
> Regards,
>   Andrea.
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: template troubles in "xx" pseudo NL website

[Marcus (OOo)]

Am 08/30/2013 04:49 PM, schrieb Rob Weir:

On Fri, Aug 30, 2013 at 10:28 AM, Ariel Constenla-Haile
  wrote:

On Fri, Aug 30, 2013 at 08:26:51AM -0400, Rob Weir wrote:

But one question:  what is the strategy on locale detection on the
download page for NL pages?  It looks like you are hardcoding it to
"es", but preserving the OS detection code?

I see:

var NL_LANGUAGE = "es";

Is that all that is needed?  We can otherwise just reuse the same scripts?


yes, var NL_LANGUAGE = ""; will default to en-US.

The download page, with all that javascript in it, is rather hard to
translate. Isn't it possible to use a cgi script (server-side vs.
client-side js)?



I assume you mean JS like this that generates the UI for the download box:

if ( LINK.toLowerCase().indexOf( "sourceforge" ) != -1 ) {
   // Download directly from a mirror with displayed platform and language.
   document.write( "" );
   document.write( "Download
Apache OpenOffice " + VERSION + ""
   + "Click here for the most recent
version for:"
   + "" + UI_PLATFORM +"  and" + LANG_ARRAY[ 2 ] +"
(~" + FILESIZE + " MByte)" );


That is a mix of HTML structure, code and language strings.  I wonder
if we could define a per-locale strings with place holders like we do
with Pootle:

"Download Apache OpenOffice %s"
"Click here for the most recent version for:"
"%s and %s (%s Megabytes)"

If we get that kind of separation, then doing the substitutions could
be done server side or client side.


As I wrote earlier I have already some kind of separation done but not 
yet committed. I'll try to commit this into the 
"http://www.openoffice.org/test/"; area on Sunday or Monday.


So, please be patient before doing maybe double work. ;-)

Thanks

Marcus


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

Yet another flyer

[Drew Jensen]

Howdy,

I needed to get my head back into thinking AOO look and feel, so decided
why not work on a flyer or two - likely this is superfluous to what you
already have however
https://docs.google.com/file/d/0Bx7ZNEXlmR0IT3JTSWZZSktzODQ

The ODT file is at
https://docs.google.com/file/d/0Bx7ZNEXlmR0INHdmVUc4cXR0Q1k

I believe that flyer is pretty much finished, but any checks/suggestions
would be appreciated.

For an A3 layout (sorry US Enlgish, so folks will want to change the
spelling to, you know - the wrong spelling ;-/ - for other places)
https://docs.google.com/file/d/0Bx7ZNEXlmR0IcmRha0tGeFVHc0U

and the ODG file is at:
https://docs.google.com/file/d/0Bx7ZNEXlmR0IajF0UVRtcHIxczg

Some will recognize the second flyer as an update to the original piece
that came out with OO.o 2.0. That file is not finished, as you will see and
anyone wanting to grab it and edit the information on any part of it -
please, please. do, just point me back to an updated version when you are
done.

Caution - if you want to successfully edit those you will need the MPlus
font, available from Sourceforge. This font, last I checked, was only
available in English and Japanese.. so a problem for other folks, I know.

//drew

Re: Yet another flyer

[Drew Jensen]

Personally, I don't care about that other entity.


On Fri, Aug 30, 2013 at 1:53 PM, David Gerard  wrote:

> On 30 August 2013 18:53, David Gerard  wrote:
>
> > Nice one! Though "OpenOffice" on its own is someone else's trademark,
> > so care should be taken in abusing it.
>
>
>
> I mean, *not* to abuse it. Sorry!
>
>
> - d.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Good to see a 4.0.1 underway

[Drew Jensen]

Hi,

Have not hit the issue tracker yet, but see that a 4.0.1 is already nearing
- good, cause this 4.0 release is pretty buggy, I'm sorry to say.

I'll toss out some of the issues I'm having and if anyone sees something
that is not in IssueTracker - grab it, cause I often miss things on
searches.

Crashes - lots crashes. (not only the guest OS [Win-Vista] but when using
Assistive Tech on the guest it twice adversely affected the host OS (Linux)
requiring a re-boot of the host - so kudos on that one - if you are going
to do it, do it right *smile*) Draw is the big problem application here.
Hangs - not as often, but a good bit - Writer is the application for that,
but it is always when manipulating a graphic. Requires hard re-boot of
Guest OS.

The application will often fail to display graphics - in all kinds of
contenxts, the actual UI main window, dialogs, PDF exports (never in a SVG
export however) and even transferring via the clipboard - all these
problems happen ONLY after an AOO session has been running for a while
(over an hour) and gets worse the more complicated the document graphics
wise. Transparency in SVG or PNG graphics seems to contribute.

The context sensitive controls become slower and slower to update as one
moves through the objects in a file over time, again it doesn't start until
the session has been running a while - eventually getting to over 5 seconds
for the controls to update - IF during this time I select a different
object (text or graphic) the application misses the change and the controls
will never update to the last selected item. [So I was on Object A, select
B, move to C before the controls update to the values for B]

GOOD news - very little data loss during the crashes (and there where over
30 hard crashes)

Bad news - on a few crashes all user data was lost, all of it, custom
colors, custom gradients, custom default template and the user
information...

Scaling grouped vector objects w/retain aspect ratio - does not work, the
final rendering is distorted (subtle, but it is there). Works fine with
multiple, grouped, bit map objects however.

Master Page side panel in Impress - I have a good number of Impress
templates (ie the old SUN template packs) and first time the Master Page
side panel is opened there is an average delay of 43 seconds before the AOO
application will respond to any user input...a bit too long I think.

Anyway - that is the short list, I have lots of screen shots but I won't
bother with that till I check the Issue tracker, and attach to existing or
a new item.. which I might not get to today, sorry.

//drew

Re: Yet another flyer

[David Gerard]

On 30 August 2013 18:46, Drew Jensen  wrote:

> I needed to get my head back into thinking AOO look and feel, so decided
> why not work on a flyer or two - likely this is superfluous to what you
> already have however
> https://docs.google.com/file/d/0Bx7ZNEXlmR0IT3JTSWZZSktzODQ



Nice one! Though "OpenOffice" on its own is someone else's trademark,
so care should be taken in abusing it.


- d.

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

Re: Yet another flyer

[David Gerard]

On 30 August 2013 18:53, David Gerard  wrote:

> Nice one! Though "OpenOffice" on its own is someone else's trademark,
> so care should be taken in abusing it.



I mean, *not* to abuse it. Sorry!


- d.

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

Embedding Fonts in SVG export

[Drew Jensen]

Hi,

Likely this is already in the IssueTracker as a RFE - but I wanted to be
very loud about this - please make this optional.

//drew

Re: Yet another flyer

[Donald Whytock]

No, but Apache cares about legal issues, and therefore might not want
someone else's trademarks (however valid or frivolous) infringed upon in
the context of presenting Apache's own valid ones.

Don


On Fri, Aug 30, 2013 at 2:08 PM, Drew Jensen wrote:

> Personally, I don't care about that other entity.
>
>
> On Fri, Aug 30, 2013 at 1:53 PM, David Gerard  wrote:
>
> > On 30 August 2013 18:53, David Gerard  wrote:
> >
> > > Nice one! Though "OpenOffice" on its own is someone else's trademark,
> > > so care should be taken in abusing it.
> >
> >
> >
> > I mean, *not* to abuse it. Sorry!
> >
> >
> > - d.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
> >
>

Re: Yet another flyer

[Drew Jensen]

Ok - I've been hearing about this for 9 years and there has never been a
problem - I was a bit curt in my reply.


On Fri, Aug 30, 2013 at 2:22 PM, Donald Whytock  wrote:

> No, but Apache cares about legal issues, and therefore might not want
> someone else's trademarks (however valid or frivolous) infringed upon in
> the context of presenting Apache's own valid ones.
>
> Don
>
>
> On Fri, Aug 30, 2013 at 2:08 PM, Drew Jensen  >wrote:
>
> > Personally, I don't care about that other entity.
> >
> >
> > On Fri, Aug 30, 2013 at 1:53 PM, David Gerard  wrote:
> >
> > > On 30 August 2013 18:53, David Gerard  wrote:
> > >
> > > > Nice one! Though "OpenOffice" on its own is someone else's trademark,
> > > > so care should be taken in abusing it.
> > >
> > >
> > >
> > > I mean, *not* to abuse it. Sorry!
> > >
> > >
> > > - d.
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > > For additional commands, e-mail: dev-h...@openoffice.apache.org
> > >
> > >
> >
>

Re: template troubles in "xx" pseudo NL website

[Marcus (OOo)]

Am 08/30/2013 04:28 PM, schrieb Ariel Constenla-Haile:

On Fri, Aug 30, 2013 at 08:26:51AM -0400, Rob Weir wrote:

But one question:  what is the strategy on locale detection on the
download page for NL pages?  It looks like you are hardcoding it to
"es", but preserving the OS detection code?

I see:

var NL_LANGUAGE = "es";

Is that all that is needed?  We can otherwise just reuse the same scripts?


yes, var NL_LANGUAGE = ""; will default to en-US.


not really. If the variable is empty then the DL scripting is trying to 
find the language from the browser data. This will be used to assemble 
the download link.



The download page, with all that javascript in it, is rather hard to
translate. Isn't it possible to use a cgi script (server-side vs.
client-side js)?


IMHO it's not really hard. You just need to put all language specific 
strings out of the JS file, put in variables instead and put the strings 
in a language-specific JS file with the respective variables.


Then you have:
- a generic "download.js" file that could be linked from the main
  download webpage
- and a language-specific one that can be located in the "xx" download
  webpage.

Maybe there a simplier solutions. However, this is the way I would go.

Marcus

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

videos again

[Drew Jensen]

I will not be able to upload any large files today, so must wait on this
another few days..

I will let you know though that I put together half a dozen small pieces
and as I looked at them it was clear that I had totally missed the mark
Look and Feel wise - so I tossed it all and started over - first going back
to some print work (the flyers) and then back to the video side and changed
from a baisc duo-tone of Blue/Black to Blue/White. (Actually I would call
the logo color Teal, but I'm a guy and so likely color blind ;)

Anyway - I've scooped up the emails from a few weeks back and will review
them at home and with luck will get back to a connection point much more
quickly this time.

Re: template troubles in "xx" pseudo NL website

[Marcus (OOo)]

Am 08/30/2013 02:26 PM, schrieb Rob Weir:

On Thu, Aug 29, 2013 at 1:08 PM, Ariel Constenla-Haile
  wrote:

On Thu, Aug 29, 2013 at 09:49:33AM -0400, Rob Weir wrote:

As I mentioned earlier I'm trying to make a self-contained English
language website that can copied and translated to make new (or
refreshed) NL websites.  This includes the 25 or so core pages that
should be translated for every language.

You can see the site here in:

https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/xx/

or a live copy here:

http://www.openoffice.org/xx/

As you can see, it is not picking up the topnav at all.  Ditto for the
side navigation on pages like:

http://www.openoffice.org/xx/why/

Any idea what I'm missing?  I've added a ssi.mdtext file into the
templates directory, e.g.,:

https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/templates/xx/ssi.mdtext


I applied the general changes to make the /xx/ site work. It had some
issues, among those mixed line endings. There are still some things to fix
(specially with links). In general, you should look at the /es/ site to
see how it should be done; there I tried to avoid relative (of the kind
../) and fixed (contenting http://www.openoffice.org/...) links, and use
the path to the site, for example:




@import url(/support/print.css);

this is less error-prone.



Thanks.  I'll take a deeper look.

But one question:  what is the strategy on locale detection on the
download page for NL pages?  It looks like you are hardcoding it to
"es", but preserving the OS detection code?

I see:

var NL_LANGUAGE = "es";

Is that all that is needed?  We can otherwise just reuse the same scripts?


Please see also the comment one line above ;-) :

// Set a specific language ISO code to force to assemble a certain 
localized build as download URL


This was a request form the Spanish NL team some months ago. They wanted 
to have the same download webpage as we have for the main one. But only 
with offering "es" builds. So, I've implemented a way to override the 
language recognition:


- Put "xx" into the variable, then only "xx" builds will be offered.
- Leave the variable empty, then it will be offered what the DL 
scripting is recognizing as browser language,


HTH

Marcus


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

Re: Yet another flyer

[Drew Jensen]

One last thing - if the group wants me to only use Apache OpenOffice - I
will.


On Fri, Aug 30, 2013 at 2:23 PM, Drew Jensen wrote:

> Ok - I've been hearing about this for 9 years and there has never been a
> problem - I was a bit curt in my reply.
>
>
> On Fri, Aug 30, 2013 at 2:22 PM, Donald Whytock wrote:
>
>> No, but Apache cares about legal issues, and therefore might not want
>> someone else's trademarks (however valid or frivolous) infringed upon in
>> the context of presenting Apache's own valid ones.
>>
>> Don
>>
>>
>> On Fri, Aug 30, 2013 at 2:08 PM, Drew Jensen > >wrote:
>>
>> > Personally, I don't care about that other entity.
>> >
>> >
>> > On Fri, Aug 30, 2013 at 1:53 PM, David Gerard 
>> wrote:
>> >
>> > > On 30 August 2013 18:53, David Gerard  wrote:
>> > >
>> > > > Nice one! Though "OpenOffice" on its own is someone else's
>> trademark,
>> > > > so care should be taken in abusing it.
>> > >
>> > >
>> > >
>> > > I mean, *not* to abuse it. Sorry!
>> > >
>> > >
>> > > - d.
>> > >
>> > > -
>> > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> > > For additional commands, e-mail: dev-h...@openoffice.apache.org
>> > >
>> > >
>> >
>>
>
>

Re: Yet another flyer

[Guy Waterval]

Hi Drew,

It is a good idea, as usual, many thanks. Just one thing, did you try to
print it in black and white to see if it could be used at the Fosdem for
instance. I can't do the test myself because I'm on hollidays  with a
minimal equipment.

A+
-- 
gw


2013/8/30 Drew Jensen 

> Howdy,
>
> I needed to get my head back into thinking AOO look and feel, so decided
> why not work on a flyer or two - likely this is superfluous to what you
> already have however
> https://docs.google.com/file/d/0Bx7ZNEXlmR0IT3JTSWZZSktzODQ
>
> The ODT file is at
> https://docs.google.com/file/d/0Bx7ZNEXlmR0INHdmVUc4cXR0Q1k
>
> I believe that flyer is pretty much finished, but any checks/suggestions
> would be appreciated.
>
> For an A3 layout (sorry US Enlgish, so folks will want to change the
> spelling to, you know - the wrong spelling ;-/ - for other places)
> https://docs.google.com/file/d/0Bx7ZNEXlmR0IcmRha0tGeFVHc0U
>
> and the ODG file is at:
> https://docs.google.com/file/d/0Bx7ZNEXlmR0IajF0UVRtcHIxczg
>
> Some will recognize the second flyer as an update to the original piece
> that came out with OO.o 2.0. That file is not finished, as you will see and
> anyone wanting to grab it and edit the information on any part of it -
> please, please. do, just point me back to an updated version when you are
> done.
>
> Caution - if you want to successfully edit those you will need the MPlus
> font, available from Sourceforge. This font, last I checked, was only
> available in English and Japanese.. so a problem for other folks, I know.
>
> //drew
>

Re: Translation integration

[janI]

On Aug 30, 2013 6:50 PM, "Michal Hriň"  wrote:
>
> Hi,
>
> I am planning this weekend to play with .sdf files.
> (converting, merging, etc.)
>
> I found some links on wiki [1],[2].
>
> Is this information still relevant ?
> There are mentioned tool "gsicheck [3]", which Juergen mention early too.
> Where can I download this tool ?
>
> [1] http://wiki.openoffice.org/wiki/Localization_for_developers
as the firdt line says, its outdated, there is a link to a updated
document. Be aware that .sdf is hopefully dead in a couple of months, look
at branch l10n40.

rgds
jan i
> [2] http://wiki.openoffice.org/wiki/Translation:General_Information
> [3] http://wiki.openoffice.org/wiki/Gsicheck
>
> Regards,
> Michal Hriň
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

Re: Yet another flyer

[Donald Whytock]

Eh, vitriol has a long half-life.  Anyway, about content...

"Issue free copies of the software to students with their course" -- I
might suggest "Provide" rather than "Issue", because for some reason I read
that as "Issue-free" on the first pass.

"book, with Writer all are simple tasks" -- suggest "book are all simple
tasks with Writer".

"straight forward" -> "straightforward"

"Exploit decorative treasures, such as special shapes such as banners,
stars and captions, from the Gallery" -> "Exploit decorative treasures,
including special shapes such as banners, stars and captions, from the
Gallery"

"Create 3D objects with A simple click" -> "Create 3D objects with a simple
click"

"Available free form:" -> "Available free from:"

I see your disclaimer box for commercial products.  I honestly don't know
if that obviates the need for TMs here and there.  Anyone else know?

Don



On Fri, Aug 30, 2013 at 2:23 PM, Drew Jensen wrote:

> Ok - I've been hearing about this for 9 years and there has never been a
> problem - I was a bit curt in my reply.
>
>
> On Fri, Aug 30, 2013 at 2:22 PM, Donald Whytock 
> wrote:
>
> > No, but Apache cares about legal issues, and therefore might not want
> > someone else's trademarks (however valid or frivolous) infringed upon in
> > the context of presenting Apache's own valid ones.
> >
> > Don
> >
> >
> > On Fri, Aug 30, 2013 at 2:08 PM, Drew Jensen  > >wrote:
> >
> > > Personally, I don't care about that other entity.
> > >
> > >
> > > On Fri, Aug 30, 2013 at 1:53 PM, David Gerard 
> wrote:
> > >
> > > > On 30 August 2013 18:53, David Gerard  wrote:
> > > >
> > > > > Nice one! Though "OpenOffice" on its own is someone else's
> trademark,
> > > > > so care should be taken in abusing it.
> > > >
> > > >
> > > >
> > > > I mean, *not* to abuse it. Sorry!
> > > >
> > > >
> > > > - d.
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > > > For additional commands, e-mail: dev-h...@openoffice.apache.org
> > > >
> > > >
> > >
> >
>

Re: [RELEASE]: new snapshot build for AOO 4.0.1

[Fernando Cassia]

On Fri, Aug 30, 2013 at 10:27 AM, Jürgen Schmidt  wrote:
>
> The wiki page is updated and for Linux you can find archive builds as
> well directly in the directory (not linked via the wiki).

Thanks for the heads up , Jürgen. Can you point us to the download
dir? Im not sure what wiki or what page within such wiki youre
referring to. I'd like to test Windows builds if possible.

FC

-- 
During times of Universal Deceit, telling the truth becomes a revolutionary act
- George Orwell

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

Re: [RELEASE]: new snapshot build for AOO 4.0.1

[Kay Schenk]

On Fri, Aug 30, 2013 at 12:34 PM, Fernando Cassia  wrote:

> On Fri, Aug 30, 2013 at 10:27 AM, Jürgen Schmidt 
> wrote:
> >
> > The wiki page is updated and for Linux you can find archive builds as
> > well directly in the directory (not linked via the wiki).
>
> Thanks for the heads up , Jürgen. Can you point us to the download
> dir? Im not sure what wiki or what page within such wiki youre
> referring to. I'd like to test Windows builds if possible.
>
> FC
>


First a BIG "THANK YOU" to Ariel for all his great Linux builds in the past!
I'm now downloading my first Linux build from the new build area.

the link to developer snapshots is:

https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds



> --
> During times of Universal Deceit, telling the truth becomes a
> revolutionary act
> - George Orwell
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
-
MzK

"When in doubt, cop an attitude."
-- Cat laws

Re: KEYS

[sebb]

On 30 August 2013 14:48, Rob Weir  wrote:
> Moving conversation over to the dev list...
>
> On Sun, Aug 25, 2013 at 8:18 PM, Ariel Constenla-Haile
>  wrote:
>> On Sun, Aug 25, 2013 at 05:31:35PM -0400, Rob Weir wrote:
>>> > I wanted to verify the
>>> > Apache_OpenOffice_4.0.0_Linux_x86-64_install-rpm_en-US.tar.gz.asc
>>> > against my download.  I downloaded the KEYS using: wget
>>> > http://www.apache.org/dist/openoffice/KEYS Then I imported the keys.
>>> >
>>> > But when I ran gpg --verify it said:
>>> >
>>> > $ gpg --verify
>>> > Apache_OpenOffice_4.0.0_Linux_x86-64_install-rpm_en-US.tar.gz.asc
>>> > gpg: Signature made Tue 16 Jul 2013 05:39:05 PM CDT using RSA
>>> > key ID B8E50356 gpg: Can't check signature: No public key
>>> >
>>> > The Key ID B8E50356 is not in the set I downloaded from your KEYS
>>> > file.  Why is it not in there??
>>> >
>>>
>>> Hi Ariel,  is B8E50356 your key?
>>
>> Yes, it is a bug that my key is not in
>> http://www.apache.org/dist/openoffice/KEYS
>>
>> This file should be a copy of

That's debatable, see below.

>> https://people.apache.org/keys/group/openoffice.asc or
>> https://people.apache.org/keys/group/openoffice-pmc.asc (in case only
>> PMC members are supposed to sign artifacts).
>>
>
> Does anyone know:  can we (may we?) do this now?  Or is this something
> to fix in 4.0.1 release?

The KEY used to sign an artifact MUST be in the KEYS file that is
linked from the download page(s).
This is something that should be checked as part of a release vote.

The files under https://people.apache.org/keys/group/ are
automatically generated from LDAP.
As such they only contain keys from current entries.
However KEYS files may still be needed to validate archive releases
where the key is not in LDAP (or the key is in LDAP but the owner is
no longer in the relevant TLP or PMC group).

For the above reasons, at present I don't think it makes sense to
blindly copy the file.

The file http://www.apache.org/dist/openoffice/KEYS has historically
been manually maintained.
New keys are added to the file as required.
Old keys are never deleted, as they may have been used for signing
archive releases.
[I guess there might be a case for deleting a compromised key]

So I suggest you just add the missing key(s) - with header info please
- to the dist/oo/KEYS file.


> -Rob
>
>
>>
>> @OP: please import the keys from
>> https://people.apache.org/keys/group/openoffice-pmc.asc
>>
>>> > Allen -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14
>>> > (GNU/Linux)
>>> >
>>> > iQEcBAEBAgAGBQJSGABoAAoJEK3AFbtYOknnVI0IALxbJlIW58Ll3R8aryWQXX4k
>>> > GJ1+Gh5cWFDYvFq9Cetz86vnxDuCaiVMxEOwnRc+PtBQHWHpzRuSKTG16fOs/5JD
>>> > SGykhVkgdkRodpiuQKE8n/kV8+/aEaa+9WpxVdn+eqhTsi3nc570JQbOaw0sCOrY
>>> > Nrdwm5Urm7w6wcP240g5UD4pjfXqAieEEe/0FdJQepikt7VFlRjsvRYVekSDHkUL
>>> > t5XgL3LQAaTt47vMM9EyPMxK2RfIG2dXUQ54phtgFs9CUt2yqVF4s8mA2Ha+moPu
>>> > rc2mS4vrKeswCO6ywyfDtaQnbaZrLxPG0y9Ql0hcUv5CEHE0eRxnJgkkTYzVUaI=
>>> > =0QtH -END PGP SIGNATURE-
>>
>> I suggest you configure Enigmail in Thunderbird to sign using PGP/MIME
>> instead of the old-fashioned inline-PGP, in Thunderbird's Account
>> Settings go to OpenPGP Options and enable "Use PGP/MIME by default", as
>> explained here http://www.rainydayz.org/content/81-account-settings
>>
>>
>> Regards
>> --
>> Ariel Constenla-Haile
>> La Plata, Argentina
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

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

[QA][Test Report] Weekly Status Update as of 20130830

[Yuzhen Fan]

Hi All,

We start doing the AOO 4.0.1 showstopper defect verification this week,
here is the weekly update (8/26 - 08/30):

*Test execution:* N/A
*
Defect summary:*
1. 15 defects are fixed and 5 defects are verified this week, so we have
25(15+15-5) in the backlog to verify -
https://issues.apache.org/ooo/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=4.0.1_release_blocker%2B%3F&sharer_id=18&list_id=85231
2. In backlog, 30 regression defects are candiate to be showstopper -
https://issues.apache.org/ooo/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=4.0.0_regression_confirmed&sharer_id=18&list_id=84503
*
Issues & quality highlight:*
1. 30 + 14 defects are waiting for fix or triage before Sep 6(the deadline
of bugfix)
2. Defect verification is with risk as no volunteer is on this work
considering potential work load on candidate defects for showstopper
*
Volunteer status:* we have 0 volunteers on showstopper verification
*
Plan for next week:*
1. Continue to verify showstopper defects
2. Continue to call for volunteers on defect verification

Any one who can contribute on showstopper defect verifcation, please let me
know!

Regards,
Yu Zhen

Re: [RELEASE]: new snapshot build for AOO 4.0.1

[sebb]

On 30 August 2013 21:36, Kay Schenk  wrote:
> On Fri, Aug 30, 2013 at 12:34 PM, Fernando Cassia  wrote:
>
>> On Fri, Aug 30, 2013 at 10:27 AM, Jürgen Schmidt 
>> wrote:
>> >
>> > The wiki page is updated and for Linux you can find archive builds as
>> > well directly in the directory (not linked via the wiki).
>>
>> Thanks for the heads up , Jürgen. Can you point us to the download
>> dir? Im not sure what wiki or what page within such wiki youre
>> referring to. I'd like to test Windows builds if possible.
>>
>> FC
>>
>
>
> First a BIG "THANK YOU" to Ariel for all his great Linux builds in the past!
> I'm now downloading my first Linux build from the new build area.
>
> the link to developer snapshots is:
>
> https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds

Great page, very easy to follow, and it does not need Javascript!
That's exactly the sort of page I think would be suitable for
downloads/other.html

However there seem to be two tables for language packs:

Snapshot Apache OpenOffice 4.0.1 - language packs

and

Apache OpenOffice - language packs

The former links appear to be full installations; that table seems to
be a repeat of

Snapshot Apache OpenOffice 4.0.1 - full installation sets

so could probably be dropped.




>
>
>> --
>> During times of Universal Deceit, telling the truth becomes a
>> revolutionary act
>> - George Orwell
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>
>
>
> --
> -
> MzK
>
> "When in doubt, cop an attitude."
> -- Cat laws

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

Re: Yet another flyer

[Rob Weir]

On Fri, Aug 30, 2013 at 2:22 PM, Donald Whytock  wrote:
> No, but Apache cares about legal issues, and therefore might not want
> someone else's trademarks (however valid or frivolous) infringed upon in
> the context of presenting Apache's own valid ones.
>

Trademarks apply to a specific class of product.  There is no other
OpenOffice, Apache OpenOffice or OpenOffice.org that is a software
application.This is why the jobs website Monster.com can exist
along with Monster Cables, or Apple Records can exist along with Apple
Computer.  So long as we use the full name at first use for clarity,
we should feel free to use the shorter form in the rest of the
document.  This has been our practice on the website, press releases,
documentation, etc.

Regards,

-Rob

> Don
>
>
> On Fri, Aug 30, 2013 at 2:08 PM, Drew Jensen 
> wrote:
>
>> Personally, I don't care about that other entity.
>>
>>
>> On Fri, Aug 30, 2013 at 1:53 PM, David Gerard  wrote:
>>
>> > On 30 August 2013 18:53, David Gerard  wrote:
>> >
>> > > Nice one! Though "OpenOffice" on its own is someone else's trademark,
>> > > so care should be taken in abusing it.
>> >
>> >
>> >
>> > I mean, *not* to abuse it. Sorry!
>> >
>> >
>> > - d.
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> > For additional commands, e-mail: dev-h...@openoffice.apache.org
>> >
>> >
>>

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

Re: Yet another flyer

[Donald Whytock]

On Fri, Aug 30, 2013 at 6:17 PM, Rob Weir  wrote:

> On Fri, Aug 30, 2013 at 2:22 PM, Donald Whytock 
> wrote:
> > No, but Apache cares about legal issues, and therefore might not want
> > someone else's trademarks (however valid or frivolous) infringed upon in
> > the context of presenting Apache's own valid ones.
> >
>
> Trademarks apply to a specific class of product.  There is no other
> OpenOffice, Apache OpenOffice or OpenOffice.org that is a software
> application.This is why the jobs website Monster.com can exist
> along with Monster Cables, or Apple Records can exist along with Apple
> Computer.  So long as we use the full name at first use for clarity,
> we should feel free to use the shorter form in the rest of the
> document.  This has been our practice on the website, press releases,
> documentation, etc.
>
>
Actually, Apple Records and Apple Computer had a very hard time existing
with each other for many years...

https://en.wikipedia.org/wiki/Apple_Corps_v._Apple_Computer

...But yeah, I can see that if you lead with Apache OpenOffice it
establishes context.  Thanks.

Don

Re: Yet another flyer

[David Gerard]

On 30 August 2013 23:17, Rob Weir  wrote:

> Trademarks apply to a specific class of product.  There is no other
> OpenOffice, Apache OpenOffice or OpenOffice.org that is a software
> application.This is why the jobs website Monster.com can exist
> along with Monster Cables, or Apple Records can exist along with Apple
> Computer.  So long as we use the full name at first use for clarity,
> we should feel free to use the shorter form in the rest of the
> document.  This has been our practice on the website, press releases,
> documentation, etc.


http://openoffice.nl/merkenregistratie

Are you quite sure this applies? I presume Apache legal have in fact
done some hard thinking on this point.


- d.

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

Re: Yet another flyer

[Rob Weir]

On Fri, Aug 30, 2013 at 7:16 PM, David Gerard  wrote:
> On 30 August 2013 23:17, Rob Weir  wrote:
>
>> Trademarks apply to a specific class of product.  There is no other
>> OpenOffice, Apache OpenOffice or OpenOffice.org that is a software
>> application.This is why the jobs website Monster.com can exist
>> along with Monster Cables, or Apple Records can exist along with Apple
>> Computer.  So long as we use the full name at first use for clarity,
>> we should feel free to use the shorter form in the rest of the
>> document.  This has been our practice on the website, press releases,
>> documentation, etc.
>
>
> http://openoffice.nl/merkenregistratie
>
> Are you quite sure this applies? I presume Apache legal have in fact
> done some hard thinking on this point.
>

The name "Apache OpenOffice" was reviewed and approved as part of the
graduation process.  We own the registered trademark for
"OpenOffice.org" as well.

So the use of a different mark "Open Office" (with a space), for a
different class of product, in a different country, is not relevant.

Regards,

-Rob

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

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