the package name itself.
Changing "Mailcap module" to "Fonts module" should do the job...
if it's just the description and it doesn't influence the code in some
way, then IMHO just go ahead and change the text to a more descriptive
one.
I just wondered if there is
Am 20.02.2018 um 22:50 schrieb Marcus:
> Am 20.02.2018 um 21:50 schrieb Matthias Seidel:
>> Am 20.02.2018 um 19:43 schrieb Marcus:
>>> Am 20.02.2018 um 17:30 schrieb Matthias Seidel:
>>>>
>>>> To be more precise, it is only the description that see
Am 20.02.2018 um 21:50 schrieb Matthias Seidel:
Am 20.02.2018 um 19:43 schrieb Marcus:
Am 20.02.2018 um 17:30 schrieb Matthias Seidel:
To be more precise, it is only the description that seems wrong, not
the package name itself.
Changing "Mailcap module" to "Fonts module&quo
Am 20.02.2018 um 19:43 schrieb Marcus:
> Am 20.02.2018 um 17:30 schrieb Matthias Seidel:
>>
>> To be more precise, it is only the description that seems wrong, not
>> the package name itself.
>>
>> Changing "Mailcap module" to "Fonts module"
Am 20.02.2018 um 17:30 schrieb Matthias Seidel:
To be more precise, it is only the description that seems wrong, not the
package name itself.
Changing "Mailcap module" to "Fonts module" should do the job...
if it's just the description and it doesn't influen
No ideas?
To be more precise, it is only the description that seems wrong, not the
package name itself.
Changing "Mailcap module" to "Fonts module" should do the job...
Regards,
Matthias
Am 13.02.2018 um 22:21 schrieb Matthias Seidel:
>
> Hi all,
>
Hi all,
when I look at:
https://svn.apache.org/repos/asf/openoffice/trunk/main/setup_native/source/packinfo/packinfo_office.txt
the package names look reasonable to me.
All except one (copied from the installed DEB package):
openoffice-ooofonts - Mailcap module for Apache OpenOffice 4.1.5
Why
On Wed, Mar 22, 2017 at 8:14 PM, Matthias Seidel wrote:
> Am 20.03.2017 um 20:01 schrieb Marcus:
> > Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic:
> >> Our pre-existing UNO components use service names of the form
> >> com.sun.star.*, for example:
> >> com.sun.star.comp.sdbc.calc.ODriver
> >>
Am 20.03.2017 um 20:01 schrieb Marcus:
> Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic:
>> Our pre-existing UNO components use service names of the form
>> com.sun.star.*, for example:
>> com.sun.star.comp.sdbc.calc.ODriver
>> com.sun.star.comp.io.TextInputStream
>> com.sun.star.comp.Calc.Spreads
Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic:
Our pre-existing UNO components use service names of the form
com.sun.star.*, for example:
com.sun.star.comp.sdbc.calc.ODriver
com.sun.star.comp.io.TextInputStream
com.sun.star.comp.Calc.SpreadsheetDocument
I am busy developing a new UNO component
One being?
On Mon, Mar 20, 2017 at 7:41 PM, Mechtilde wrote:
> Hello,
>
> do you know the existing one?
>
> Regards
>
> Mechtilde
>
>
> Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic:
> > Hi
> >
> > Our pre-existing UNO components use service names of the form
> > com.sun.star.*, for example:
>
Hi Damjan,
If this an official part of AOO then why not org.apache.openoffice.uno.*?
Regards,
Dave
> On Mar 20, 2017, at 10:41 AM, Mechtilde wrote:
>
> Hello,
>
> do you know the existing one?
>
> Regards
>
> Mechtilde
>
>
> Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic:
>> Hi
>>
>> Ou
Hello,
do you know the existing one?
Regards
Mechtilde
Am 20.03.2017 um 16:40 schrieb Damjan Jovanovic:
> Hi
>
> Our pre-existing UNO components use service names of the form
> com.sun.star.*, for example:
> com.sun.star.comp.sdbc.calc.ODriver
> com.sun.star.comp.io.TextInputStream
> com.sun.s
Hi
Our pre-existing UNO components use service names of the form
com.sun.star.*, for example:
com.sun.star.comp.sdbc.calc.ODriver
com.sun.star.comp.io.TextInputStream
com.sun.star.comp.Calc.SpreadsheetDocument
I am busy developing a new UNO component, a database driver for PostgreSQL.
Should I ra
a question about the product version in installation package
>> name,
>> is the version controlled by "aoo.ver" in srcrelease.xml under folder
>> https://svn.apache.org/repos/**asf/incubator/ooo/trunk/main/**
>> solenv/bin/srcrelease.xml<https://svn.apache.org/re
Hi
On 2013/04/11 4:50 PM, Ji Yan wrote:
I have a question about the product version in installation package name,
is the version controlled by "aoo.ver" in srcrelease.xml under folder
https://svn.apache.org/repos/asf/incubator/ooo/trunk/main/solenv/bin/srcrelease.xml
Please n
On 4/11/13 4:59 PM, Jürgen Schmidt wrote:
> On 4/11/13 4:58 PM, Jürgen Schmidt wrote:
>> On 4/11/13 4:50 PM, Ji Yan wrote:
>>> Hi all,
>>>
>>> I have a question about the product version in installation package name,
>>> is the version controlle
On 4/11/13 4:58 PM, Jürgen Schmidt wrote:
> On 4/11/13 4:50 PM, Ji Yan wrote:
>> Hi all,
>>
>> I have a question about the product version in installation package name,
>> is the version controlled by "aoo.ver" in srcrelease.xml under folder
>> htt
On 4/11/13 4:50 PM, Ji Yan wrote:
> Hi all,
>
> I have a question about the product version in installation package name,
> is the version controlled by "aoo.ver" in srcrelease.xml under folder
> https://svn.apache.org/repos/asf/incubator/ooo/trunk/main/solenv/bin/srcr
Hi all,
I have a question about the product version in installation package name,
is the version controlled by "aoo.ver" in srcrelease.xml under folder
https://svn.apache.org/repos/asf/incubator/ooo/trunk/main/solenv/bin/srcrelease.xml
Currently, the version is "3.5", sh
20 matches
Mail list logo
