New grammar checking framework available with OOo300 m14

classic Classic list List threaded Threaded
29 messages Options
12
Reply | Threaded
Open this post in threaded view
|

New grammar checking framework available with OOo300 m14

thomas.lange

Hi all,

The OOo300 m14 build will feature our latest changes to the grammar
checking API and framework. Especially the API should now remain
unchanged for the forseeable future. The frame and UI of course will and
should still undergo some improvements in the next releases of OOo.

Since there were at least one or two changes to the API that required us
to become incompatible with grammar checking API used in OOo 3.0 we took
the liberty to even make some more changes, usually cleanups and name
changes only, to the API as well.
With OOo 3.0.1 all the API named XGrammarCheck{er|ing}*.idl is no longer
available and replaced with new API files named XProofread{er|ing}*.idl


In more detail it looks like this:

new API:

com/sun/star/text/XMultiTextMarkup
com/sun/star/text/TextMarkupDescriptor

com/sun/star/linguistic2/ProofreadingIterator
com/sun/star/linguistic2/XProofreadingIterator

com/sun/star/linguistic2/Proofreader
com/sun/star/linguistic2/XProofreader
com/sun/star/linguistic2/ProofreadingResult
com/sun/star/linguistic2/SingleProofreadingError


modified API:

com/sun/star/linguistic2/LinguServiceEventFlags
  PROOFREAD_AGAIN added


If you want to implement a Proofreader (or change your existing grammar
checker) for use with OOo 3.0.1 it should be
sufficient to read about the last 5 interfaces (starting with
Proofreader) only.

Of course the OOo minimal version for those new extensions should be OOo
3.0.1.


I surely look forward to the see all the new proofreading extensions
next year. Especially I hope it will be a rather smooth change for
CoGrOO, and Language Tool since those two were already available for OOo
3.0 as extensions and I like to see them with OOo 3.0.1 again. ;-)
And thank you so much for all your great work for OOo!


Regards,
Thomas


PS: if you have urgent question about proofreading please drop me a mail
as well, since I will be out of the office for the next about 2,5 weeks
and not reading this newsgroup in that time. I will have an occasional
look at my email account and see if there is sth. coming up that can be
answered from out-of-the-office.




---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Németh László-2
Hi Thomas,

Great news. Is there any testing/demo C++ component for the new Grammar
Checker API to develop a very simple language-neutral grammar checker in
C/C++?

Thanks,
László


2008/12/18 Thomas Lange - Sun Germany - ham02 - Hamburg <
[hidden email]>

>
> Hi all,
>
> The OOo300 m14 build will feature our latest changes to the grammar
> checking API and framework. Especially the API should now remain
> unchanged for the forseeable future. The frame and UI of course will and
> should still undergo some improvements in the next releases of OOo.
>
> Since there were at least one or two changes to the API that required us
> to become incompatible with grammar checking API used in OOo 3.0 we took
> the liberty to even make some more changes, usually cleanups and name
> changes only, to the API as well.
> With OOo 3.0.1 all the API named XGrammarCheck{er|ing}*.idl is no longer
> available and replaced with new API files named XProofread{er|ing}*.idl
>
>
> In more detail it looks like this:
>
> new API:
>
> com/sun/star/text/XMultiTextMarkup
> com/sun/star/text/TextMarkupDescriptor
>
> com/sun/star/linguistic2/ProofreadingIterator
> com/sun/star/linguistic2/XProofreadingIterator
>
> com/sun/star/linguistic2/Proofreader
> com/sun/star/linguistic2/XProofreader
> com/sun/star/linguistic2/ProofreadingResult
> com/sun/star/linguistic2/SingleProofreadingError
>
>
> modified API:
>
> com/sun/star/linguistic2/LinguServiceEventFlags
>  PROOFREAD_AGAIN added
>
>
> If you want to implement a Proofreader (or change your existing grammar
> checker) for use with OOo 3.0.1 it should be
> sufficient to read about the last 5 interfaces (starting with
> Proofreader) only.
>
> Of course the OOo minimal version for those new extensions should be OOo
> 3.0.1.
>
>
> I surely look forward to the see all the new proofreading extensions
> next year. Especially I hope it will be a rather smooth change for
> CoGrOO, and Language Tool since those two were already available for OOo
> 3.0 as extensions and I like to see them with OOo 3.0.1 again. ;-)
> And thank you so much for all your great work for OOo!
>
>
> Regards,
> Thomas
>
>
> PS: if you have urgent question about proofreading please drop me a mail
> as well, since I will be out of the office for the next about 2,5 weeks
> and not reading this newsgroup in that time. I will have an occasional
> look at my email account and see if there is sth. coming up that can be
> answered from out-of-the-office.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Ruud Baars-2
Laszlo,

Are you planning to cooperate with Daniel and Marcin of LanguageTool ?

Ruud

Németh László schreef:

> Hi Thomas,
>
> Great news. Is there any testing/demo C++ component for the new Grammar
> Checker API to develop a very simple language-neutral grammar checker in
> C/C++?
>
> Thanks,
> László
>
>
> 2008/12/18 Thomas Lange - Sun Germany - ham02 - Hamburg <
> [hidden email]>
>
>  
>> Hi all,
>>
>> The OOo300 m14 build will feature our latest changes to the grammar
>> checking API and framework. Especially the API should now remain
>> unchanged for the forseeable future. The frame and UI of course will and
>> should still undergo some improvements in the next releases of OOo.
>>
>> Since there were at least one or two changes to the API that required us
>> to become incompatible with grammar checking API used in OOo 3.0 we took
>> the liberty to even make some more changes, usually cleanups and name
>> changes only, to the API as well.
>> With OOo 3.0.1 all the API named XGrammarCheck{er|ing}*.idl is no longer
>> available and replaced with new API files named XProofread{er|ing}*.idl
>>
>>
>> In more detail it looks like this:
>>
>> new API:
>>
>> com/sun/star/text/XMultiTextMarkup
>> com/sun/star/text/TextMarkupDescriptor
>>
>> com/sun/star/linguistic2/ProofreadingIterator
>> com/sun/star/linguistic2/XProofreadingIterator
>>
>> com/sun/star/linguistic2/Proofreader
>> com/sun/star/linguistic2/XProofreader
>> com/sun/star/linguistic2/ProofreadingResult
>> com/sun/star/linguistic2/SingleProofreadingError
>>
>>
>> modified API:
>>
>> com/sun/star/linguistic2/LinguServiceEventFlags
>>  PROOFREAD_AGAIN added
>>
>>
>> If you want to implement a Proofreader (or change your existing grammar
>> checker) for use with OOo 3.0.1 it should be
>> sufficient to read about the last 5 interfaces (starting with
>> Proofreader) only.
>>
>> Of course the OOo minimal version for those new extensions should be OOo
>> 3.0.1.
>>
>>
>> I surely look forward to the see all the new proofreading extensions
>> next year. Especially I hope it will be a rather smooth change for
>> CoGrOO, and Language Tool since those two were already available for OOo
>> 3.0 as extensions and I like to see them with OOo 3.0.1 again. ;-)
>> And thank you so much for all your great work for OOo!
>>
>>
>> Regards,
>> Thomas
>>
>>
>> PS: if you have urgent question about proofreading please drop me a mail
>> as well, since I will be out of the office for the next about 2,5 weeks
>> and not reading this newsgroup in that time. I will have an occasional
>> look at my email account and see if there is sth. coming up that can be
>> answered from out-of-the-office.
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>    
>
>  
Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

thomas.lange
In reply to this post by thomas.lange

Hi all,

> Laszlo,
>
> Are you planning to cooperate with Daniel and Marcin of LanguageTool ?
>
> Ruud
>
> Németh László schreef:
>> Hi Thomas,
>>
>> Great news. Is there any testing/demo C++ component for the new Grammar
>> Checker API to develop a very simple language-neutral grammar checker in
>> C/C++?


In linguistic/source is a grammarchecker.?xx dummy implementation that
used to work with the older 3.0 API. But it is currently not being build
because it was not adapted to the new API and did not yet undergo a
serious second review of how things are done there.
Wee plan to do that next year in order to have a sample from scratch to
build upon.

If you do not want to wait you may modify it to make use of the new API
while still having a cautious look on how it does things.


->Nemeth: BTW, for some odd reason I did nor saw your posting in the ML
but only the above reply to it.


Regards,
Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Németh László-2
In reply to this post by Ruud Baars-2
Hi,

2008/12/18 r.j.baars <[hidden email]>

> Laszlo,
>
> Are you planning to cooperate with Daniel and Marcin of LanguageTool ?


Yes, I am. My plan is to develop a lightweight grammar checker for the
simple sentence level spell checking tasks, like recognition of the trivial
punctuation errors etc. with a simplified data format (In fact, before
punctuation checking in some languages, it would be fine to fix this and
similar problems: automatic non breaking spaces before French punctuation:
http://www.openoffice.org/issues/show_bug.cgi?id=17169). However, default
LanguageTool integration is much better for the languages supported by
LanguageTool, especially because my plan is only an idea yet.

Regards,
László

>
>
> Ruud
>
> Németh László schreef:
>
>  Hi Thomas,
>>
>> Great news. Is there any testing/demo C++ component for the new Grammar
>> Checker API to develop a very simple language-neutral grammar checker in
>> C/C++?
>>
>> Thanks,
>> László
>>
>>
>> 2008/12/18 Thomas Lange - Sun Germany - ham02 - Hamburg <
>> [hidden email]>
>>
>>
>>
>>> Hi all,
>>>
>>> The OOo300 m14 build will feature our latest changes to the grammar
>>> checking API and framework. Especially the API should now remain
>>> unchanged for the forseeable future. The frame and UI of course will and
>>> should still undergo some improvements in the next releases of OOo.
>>>
>>> Since there were at least one or two changes to the API that required us
>>> to become incompatible with grammar checking API used in OOo 3.0 we took
>>> the liberty to even make some more changes, usually cleanups and name
>>> changes only, to the API as well.
>>> With OOo 3.0.1 all the API named XGrammarCheck{er|ing}*.idl is no longer
>>> available and replaced with new API files named XProofread{er|ing}*.idl
>>>
>>>
>>> In more detail it looks like this:
>>>
>>> new API:
>>>
>>> com/sun/star/text/XMultiTextMarkup
>>> com/sun/star/text/TextMarkupDescriptor
>>>
>>> com/sun/star/linguistic2/ProofreadingIterator
>>> com/sun/star/linguistic2/XProofreadingIterator
>>>
>>> com/sun/star/linguistic2/Proofreader
>>> com/sun/star/linguistic2/XProofreader
>>> com/sun/star/linguistic2/ProofreadingResult
>>> com/sun/star/linguistic2/SingleProofreadingError
>>>
>>>
>>> modified API:
>>>
>>> com/sun/star/linguistic2/LinguServiceEventFlags
>>>  PROOFREAD_AGAIN added
>>>
>>>
>>> If you want to implement a Proofreader (or change your existing grammar
>>> checker) for use with OOo 3.0.1 it should be
>>> sufficient to read about the last 5 interfaces (starting with
>>> Proofreader) only.
>>>
>>> Of course the OOo minimal version for those new extensions should be OOo
>>> 3.0.1.
>>>
>>>
>>> I surely look forward to the see all the new proofreading extensions
>>> next year. Especially I hope it will be a rather smooth change for
>>> CoGrOO, and Language Tool since those two were already available for OOo
>>> 3.0 as extensions and I like to see them with OOo 3.0.1 again. ;-)
>>> And thank you so much for all your great work for OOo!
>>>
>>>
>>> Regards,
>>> Thomas
>>>
>>>
>>> PS: if you have urgent question about proofreading please drop me a mail
>>> as well, since I will be out of the office for the next about 2,5 weeks
>>> and not reading this newsgroup in that time. I will have an occasional
>>> look at my email account and see if there is sth. coming up that can be
>>> answered from out-of-the-office.
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>>
>>>
>>
>>
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Németh László-2
In reply to this post by thomas.lange
Hi,

2008/12/19 Thomas Lange - Sun Germany - ham02 - Hamburg <[hidden email]>:

>
> Hi all,
>
>> Laszlo,
>>
>> Are you planning to cooperate with Daniel and Marcin of LanguageTool ?
>>
>> Ruud
>>
>> Németh László schreef:
>>> Hi Thomas,
>>>
>>> Great news. Is there any testing/demo C++ component for the new Grammar
>>> Checker API to develop a very simple language-neutral grammar checker in
>>> C/C++?
>
>
> In linguistic/source is a grammarchecker.?xx dummy implementation that
> used to work with the older 3.0 API. But it is currently not being build
> because it was not adapted to the new API and did not yet undergo a
> serious second review of how things are done there.
> Wee plan to do that next year in order to have a sample from scratch to
> build upon.

Thanks, I'm glad of it.

>
> If you do not want to wait you may modify it to make use of the new API
> while still having a cautious look on how it does things.
>
>
> ->Nemeth: BTW, for some odd reason I did nor saw your posting in the ML
> but only the above reply to it.

It's no problem. Sorry for my unanswered mails, too. I have just find
again your letter about the multiple dictionaries supported by the
same locale in OpenOffice.org 3. I have checked both of the available
en_US dictionary extensions, and they work well together:

OpenMedSpel (en-us) - OpenSource Medical Spelling
http://extensions.services.openoffice.org/project/OMS

English Names Dictionary en_US
http://extensions.services.openoffice.org/project/US_Names_Dictionary

Regards,
László

>
>
> Regards,
> Thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Ruud Baars-2
In reply to this post by Németh László-2
There is one area where hunspell and LT are both in.
For Dutch, I made rules for words that are ok, but only in combinations.
Like latin combinations as 'et cetera, 'nota bene',. but also
oldfasioned expressions as 'ter zake', where zake is often missspelled.

It would help to expand Hunspell/the spellchecker into the area of
triword checking, which is not really grammar, but still multiword checking.

Ruud.

Németh László schreef:

> Hi,
>
> 2008/12/18 r.j.baars <[hidden email]>
>
>  
>> Laszlo,
>>
>> Are you planning to cooperate with Daniel and Marcin of LanguageTool ?
>>    
>
>
> Yes, I am. My plan is to develop a lightweight grammar checker for the
> simple sentence level spell checking tasks, like recognition of the trivial
> punctuation errors etc. with a simplified data format (In fact, before
> punctuation checking in some languages, it would be fine to fix this and
> similar problems: automatic non breaking spaces before French punctuation:
> http://www.openoffice.org/issues/show_bug.cgi?id=17169). However, default
> LanguageTool integration is much better for the languages supported by
> LanguageTool, especially because my plan is only an idea yet.
>
> Regards,
> László
>
>  
>> Ruud
>>
>> Németh László schreef:
>>
>>  Hi Thomas,
>>    
>>> Great news. Is there any testing/demo C++ component for the new Grammar
>>> Checker API to develop a very simple language-neutral grammar checker in
>>> C/C++?
>>>
>>> Thanks,
>>> László
>>>
>>>
>>> 2008/12/18 Thomas Lange - Sun Germany - ham02 - Hamburg <
>>> [hidden email]>
>>>
>>>
>>>
>>>      
>>>> Hi all,
>>>>
>>>> The OOo300 m14 build will feature our latest changes to the grammar
>>>> checking API and framework. Especially the API should now remain
>>>> unchanged for the forseeable future. The frame and UI of course will and
>>>> should still undergo some improvements in the next releases of OOo.
>>>>
>>>> Since there were at least one or two changes to the API that required us
>>>> to become incompatible with grammar checking API used in OOo 3.0 we took
>>>> the liberty to even make some more changes, usually cleanups and name
>>>> changes only, to the API as well.
>>>> With OOo 3.0.1 all the API named XGrammarCheck{er|ing}*.idl is no longer
>>>> available and replaced with new API files named XProofread{er|ing}*.idl
>>>>
>>>>
>>>> In more detail it looks like this:
>>>>
>>>> new API:
>>>>
>>>> com/sun/star/text/XMultiTextMarkup
>>>> com/sun/star/text/TextMarkupDescriptor
>>>>
>>>> com/sun/star/linguistic2/ProofreadingIterator
>>>> com/sun/star/linguistic2/XProofreadingIterator
>>>>
>>>> com/sun/star/linguistic2/Proofreader
>>>> com/sun/star/linguistic2/XProofreader
>>>> com/sun/star/linguistic2/ProofreadingResult
>>>> com/sun/star/linguistic2/SingleProofreadingError
>>>>
>>>>
>>>> modified API:
>>>>
>>>> com/sun/star/linguistic2/LinguServiceEventFlags
>>>>  PROOFREAD_AGAIN added
>>>>
>>>>
>>>> If you want to implement a Proofreader (or change your existing grammar
>>>> checker) for use with OOo 3.0.1 it should be
>>>> sufficient to read about the last 5 interfaces (starting with
>>>> Proofreader) only.
>>>>
>>>> Of course the OOo minimal version for those new extensions should be OOo
>>>> 3.0.1.
>>>>
>>>>
>>>> I surely look forward to the see all the new proofreading extensions
>>>> next year. Especially I hope it will be a rather smooth change for
>>>> CoGrOO, and Language Tool since those two were already available for OOo
>>>> 3.0 as extensions and I like to see them with OOo 3.0.1 again. ;-)
>>>> And thank you so much for all your great work for OOo!
>>>>
>>>>
>>>> Regards,
>>>> Thomas
>>>>
>>>>
>>>> PS: if you have urgent question about proofreading please drop me a mail
>>>> as well, since I will be out of the office for the next about 2,5 weeks
>>>> and not reading this newsgroup in that time. I will have an occasional
>>>> look at my email account and see if there is sth. coming up that can be
>>>> answered from out-of-the-office.
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>>
>>>>
>>>>        
>>>
>>>      
>
>  
Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

William Colen
In reply to this post by thomas.lange
Does the ServiceManager "GrammarCheckers" we have to configure in
Linguistic.xcu still the same?
Thank you,
William Colen


On Thu, Dec 18, 2008 at 7:44 AM, Thomas Lange - Sun Germany - ham02 -
Hamburg <[hidden email]> wrote:

>
> Hi all,
>
> The OOo300 m14 build will feature our latest changes to the grammar
> checking API and framework. Especially the API should now remain
> unchanged for the forseeable future. The frame and UI of course will and
> should still undergo some improvements in the next releases of OOo.
>
> Since there were at least one or two changes to the API that required us
> to become incompatible with grammar checking API used in OOo 3.0 we took
> the liberty to even make some more changes, usually cleanups and name
> changes only, to the API as well.
> With OOo 3.0.1 all the API named XGrammarCheck{er|ing}*.idl is no longer
> available and replaced with new API files named XProofread{er|ing}*.idl
>
>
> In more detail it looks like this:
>
> new API:
>
> com/sun/star/text/XMultiTextMarkup
> com/sun/star/text/TextMarkupDescriptor
>
> com/sun/star/linguistic2/ProofreadingIterator
> com/sun/star/linguistic2/XProofreadingIterator
>
> com/sun/star/linguistic2/Proofreader
> com/sun/star/linguistic2/XProofreader
> com/sun/star/linguistic2/ProofreadingResult
> com/sun/star/linguistic2/SingleProofreadingError
>
>
> modified API:
>
> com/sun/star/linguistic2/LinguServiceEventFlags
>  PROOFREAD_AGAIN added
>
>
> If you want to implement a Proofreader (or change your existing grammar
> checker) for use with OOo 3.0.1 it should be
> sufficient to read about the last 5 interfaces (starting with
> Proofreader) only.
>
> Of course the OOo minimal version for those new extensions should be OOo
> 3.0.1.
>
>
> I surely look forward to the see all the new proofreading extensions
> next year. Especially I hope it will be a rather smooth change for
> CoGrOO, and Language Tool since those two were already available for OOo
> 3.0 as extensions and I like to see them with OOo 3.0.1 again. ;-)
> And thank you so much for all your great work for OOo!
>
>
> Regards,
> Thomas
>
>
> PS: if you have urgent question about proofreading please drop me a mail
> as well, since I will be out of the office for the next about 2,5 weeks
> and not reading this newsgroup in that time. I will have an occasional
> look at my email account and see if there is sth. coming up that can be
> answered from out-of-the-office.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

thomas.lange
In reply to this post by thomas.lange

Hi William!

William Colen wrote:

> Does the ServiceManager "GrammarCheckers" we have to configure in
> Linguistic.xcu still the same?
> Thank you,
> William Colen


If your question is if you still need an entry like

    <node oor:name="ServiceManager">
        <node oor:name="GrammarCheckers">
            <node oor:name="net.myprivate.www.PersonalGrammarChecker"
oor:op="fuse">
                <prop oor:name="Locales" oor:type="oor:string-list">
                    <value>en-US en-GB en-AU</value>
                </prop>
            </node>
        </node>
    </node>

then the answer is 'yes'. This is the way to tell OOo which grammar
checkers are available.


Thomas


>
>
> On Thu, Dec 18, 2008 at 7:44 AM, Thomas Lange - Sun Germany - ham02 -
> Hamburg <[hidden email]> wrote:
>
>>
>> Hi all,
>>
>> The OOo300 m14 build will feature our latest changes to the grammar
>> checking API and framework. Especially the API should now remain
>> unchanged for the forseeable future. The frame and UI of course will and
>> should still undergo some improvements in the next releases of OOo.
>>
>> Since there were at least one or two changes to the API that required us
>> to become incompatible with grammar checking API used in OOo 3.0 we took
>> the liberty to even make some more changes, usually cleanups and name
>> changes only, to the API as well.
>> With OOo 3.0.1 all the API named XGrammarCheck{er|ing}*.idl is no longer
>> available and replaced with new API files named XProofread{er|ing}*.idl
>>
>>
>> In more detail it looks like this:
>>
>> new API:
>>
>> com/sun/star/text/XMultiTextMarkup
>> com/sun/star/text/TextMarkupDescriptor
>>
>> com/sun/star/linguistic2/ProofreadingIterator
>> com/sun/star/linguistic2/XProofreadingIterator
>>
>> com/sun/star/linguistic2/Proofreader
>> com/sun/star/linguistic2/XProofreader
>> com/sun/star/linguistic2/ProofreadingResult
>> com/sun/star/linguistic2/SingleProofreadingError
>>
>>
>> modified API:
>>
>> com/sun/star/linguistic2/LinguServiceEventFlags
>>  PROOFREAD_AGAIN added
>>
>>
>> If you want to implement a Proofreader (or change your existing grammar
>> checker) for use with OOo 3.0.1 it should be
>> sufficient to read about the last 5 interfaces (starting with
>> Proofreader) only.
>>
>> Of course the OOo minimal version for those new extensions should be OOo
>> 3.0.1.
>>
>>
>> I surely look forward to the see all the new proofreading extensions
>> next year. Especially I hope it will be a rather smooth change for
>> CoGrOO, and Language Tool since those two were already available for OOo
>> 3.0 as extensions and I like to see them with OOo 3.0.1 again. ;-)
>> And thank you so much for all your great work for OOo!
>>
>>
>> Regards,
>> Thomas
>>
>>
>> PS: if you have urgent question about proofreading please drop me a mail
>> as well, since I will be out of the office for the next about 2,5 weeks
>> and not reading this newsgroup in that time. I will have an occasional
>> look at my email account and see if there is sth. coming up that can be
>> answered from out-of-the-office.
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

William Colen
Thank you Thomas,
I could figure it out. At that time, my grammar checker wasn't working and I
was trying to find what was going wrong.
Cogroo still not working with OOo 3.0.1. The OOo Writer crashes just after I
press F7, and the automatic checking is not working. I'm probably missing
something.

Naber/Marcin
Could you make LT work with OOo 3.0.1?

Thank you,
William


On Wed, Jan 7, 2009 at 7:40 AM, Thomas Lange - Sun Germany - ham02 - Hamburg
<[hidden email]> wrote:

>
> Hi William!
>
> William Colen wrote:
>
> > Does the ServiceManager "GrammarCheckers" we have to configure in
> > Linguistic.xcu still the same?
> > Thank you,
> > William Colen
>
>
> If your question is if you still need an entry like
>
>    <node oor:name="ServiceManager">
>        <node oor:name="GrammarCheckers">
>            <node oor:name="net.myprivate.www.PersonalGrammarChecker"
> oor:op="fuse">
>                <prop oor:name="Locales" oor:type="oor:string-list">
>                    <value>en-US en-GB en-AU</value>
>                </prop>
>            </node>
>        </node>
>    </node>
>
> then the answer is 'yes'. This is the way to tell OOo which grammar
> checkers are available.
>
>
> Thomas
>
>
> >
> >
> > On Thu, Dec 18, 2008 at 7:44 AM, Thomas Lange - Sun Germany - ham02 -
> > Hamburg <[hidden email]> wrote:
> >
> >>
> >> Hi all,
> >>
> >> The OOo300 m14 build will feature our latest changes to the grammar
> >> checking API and framework. Especially the API should now remain
> >> unchanged for the forseeable future. The frame and UI of course will and
> >> should still undergo some improvements in the next releases of OOo.
> >>
> >> Since there were at least one or two changes to the API that required us
> >> to become incompatible with grammar checking API used in OOo 3.0 we took
> >> the liberty to even make some more changes, usually cleanups and name
> >> changes only, to the API as well.
> >> With OOo 3.0.1 all the API named XGrammarCheck{er|ing}*.idl is no longer
> >> available and replaced with new API files named XProofread{er|ing}*.idl
> >>
> >>
> >> In more detail it looks like this:
> >>
> >> new API:
> >>
> >> com/sun/star/text/XMultiTextMarkup
> >> com/sun/star/text/TextMarkupDescriptor
> >>
> >> com/sun/star/linguistic2/ProofreadingIterator
> >> com/sun/star/linguistic2/XProofreadingIterator
> >>
> >> com/sun/star/linguistic2/Proofreader
> >> com/sun/star/linguistic2/XProofreader
> >> com/sun/star/linguistic2/ProofreadingResult
> >> com/sun/star/linguistic2/SingleProofreadingError
> >>
> >>
> >> modified API:
> >>
> >> com/sun/star/linguistic2/LinguServiceEventFlags
> >>  PROOFREAD_AGAIN added
> >>
> >>
> >> If you want to implement a Proofreader (or change your existing grammar
> >> checker) for use with OOo 3.0.1 it should be
> >> sufficient to read about the last 5 interfaces (starting with
> >> Proofreader) only.
> >>
> >> Of course the OOo minimal version for those new extensions should be OOo
> >> 3.0.1.
> >>
> >>
> >> I surely look forward to the see all the new proofreading extensions
> >> next year. Especially I hope it will be a rather smooth change for
> >> CoGrOO, and Language Tool since those two were already available for OOo
> >> 3.0 as extensions and I like to see them with OOo 3.0.1 again. ;-)
> >> And thank you so much for all your great work for OOo!
> >>
> >>
> >> Regards,
> >> Thomas
> >>
> >>
> >> PS: if you have urgent question about proofreading please drop me a mail
> >> as well, since I will be out of the office for the next about 2,5 weeks
> >> and not reading this newsgroup in that time. I will have an occasional
> >> look at my email account and see if there is sth. coming up that can be
> >> answered from out-of-the-office.
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
> >
>
>
Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Marcin Miłkowski
William Colen pisze:
> Thank you Thomas,
> I could figure it out. At that time, my grammar checker wasn't working and I
> was trying to find what was going wrong.
> Cogroo still not working with OOo 3.0.1. The OOo Writer crashes just after I
> press F7, and the automatic checking is not working. I'm probably missing
> something.
>
> Naber/Marcin
> Could you make LT work with OOo 3.0.1?

Yes, it works flawlessly as far as I can see. Just look at Main.java:

http://languagetool.cvs.sourceforge.net/viewvc/languagetool/JLanguageTool/src/java/de/danielnaber/languagetool/openoffice/Main.java?view=markup

Note: you must remove all previous Cogroo version before you install
3.0.1 - it cannot be uninstalled from OOo after due to API change.

Regards,
Marcin

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Michel Weimerskirch
In reply to this post by thomas.lange
Hi

Is there a minimalistic Java example available that uses the new API?

I am willing to port an old proofreading tool that I wrote for OOo2
(that corrects a specific phonological rule in Luxembourgish) to
OOo3.0.1, so an example application could help me get started.

Regards,
Michel

On Thu, Dec 18, 2008 at 10:44 AM, Thomas Lange - Sun Germany - ham02 -
Hamburg <[hidden email]> wrote:

>
> Hi all,
>
> The OOo300 m14 build will feature our latest changes to the grammar
> checking API and framework. Especially the API should now remain
> unchanged for the forseeable future. The frame and UI of course will and
> should still undergo some improvements in the next releases of OOo.
>
> Since there were at least one or two changes to the API that required us
> to become incompatible with grammar checking API used in OOo 3.0 we took
> the liberty to even make some more changes, usually cleanups and name
> changes only, to the API as well.
> With OOo 3.0.1 all the API named XGrammarCheck{er|ing}*.idl is no longer
> available and replaced with new API files named XProofread{er|ing}*.idl
>
>
> In more detail it looks like this:
>
> new API:
>
> com/sun/star/text/XMultiTextMarkup
> com/sun/star/text/TextMarkupDescriptor
>
> com/sun/star/linguistic2/ProofreadingIterator
> com/sun/star/linguistic2/XProofreadingIterator
>
> com/sun/star/linguistic2/Proofreader
> com/sun/star/linguistic2/XProofreader
> com/sun/star/linguistic2/ProofreadingResult
> com/sun/star/linguistic2/SingleProofreadingError
>
>
> modified API:
>
> com/sun/star/linguistic2/LinguServiceEventFlags
>  PROOFREAD_AGAIN added
>
>
> If you want to implement a Proofreader (or change your existing grammar
> checker) for use with OOo 3.0.1 it should be
> sufficient to read about the last 5 interfaces (starting with
> Proofreader) only.
>
> Of course the OOo minimal version for those new extensions should be OOo
> 3.0.1.
>
>
> I surely look forward to the see all the new proofreading extensions
> next year. Especially I hope it will be a rather smooth change for
> CoGrOO, and Language Tool since those two were already available for OOo
> 3.0 as extensions and I like to see them with OOo 3.0.1 again. ;-)
> And thank you so much for all your great work for OOo!
>
>
> Regards,
> Thomas
>
>
> PS: if you have urgent question about proofreading please drop me a mail
> as well, since I will be out of the office for the next about 2,5 weeks
> and not reading this newsgroup in that time. I will have an occasional
> look at my email account and see if there is sth. coming up that can be
> answered from out-of-the-office.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Carlos Menezes
In reply to this post by thomas.lange
Thomas,

We are trying to debug new version of CoGrOO (3.0.2) but it sounds a
bit difficult.

menezes@possante:~$ /opt/broffice.org3/program/soffice -writer
terminate called after throwing an instance of
'com::sun::star::uno::RuntimeException'
sh: crash_report: not found

Do you have any tip to easy this task?

[]s,

Menezes

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Carlos Menezes
2009/1/8, CARLOS EDUARDO DANTAS DE MENEZES <[hidden email]>:

> Thomas,
>
> We are trying to debug new version of CoGrOO (3.0.2) but it sounds a
> bit difficult.
>
> menezes@possante:~$ /opt/broffice.org3/program/soffice -writer
> terminate called after throwing an instance of
> 'com::sun::star::uno::RuntimeException'
> sh: crash_report: not found
>
> Do you have any tip to easy this task?
>
> []s,
>
> Menezes
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

thomas.lange

Hello Carlos,

> > We are trying to debug new version of CoGrOO (3.0.2) but it sounds a
> > bit difficult.
> >
> > menezes@possante:~$ /opt/broffice.org3/program/soffice -writer
> > terminate called after throwing an instance of
> > 'com::sun::star::uno::RuntimeException'
> > sh: crash_report: not found
> >
> > Do you have any tip to easy this task?
>  
Not really.
Seems it will be required to debug the OOo C++ code in order to see
where that exception gets thrown and why.

If you can describe a scenario for the problem and also provide me with
a download link for the CoGrOO extension I will try to have a look into
it tomorrow or Monday morning. Otherwise you probably need to debug the
C++ side yourself.


Regards,
Thomas



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Ruud Baars-2
In reply to this post by Michel Weimerskirch
Adding luxembourgish to Languagetool, is that an option ?

Ruud

Michel Weimerskirch schreef:

> Hi
>
> Is there a minimalistic Java example available that uses the new API?
>
> I am willing to port an old proofreading tool that I wrote for OOo2
> (that corrects a specific phonological rule in Luxembourgish) to
> OOo3.0.1, so an example application could help me get started.
>
> Regards,
> Michel
>
> On Thu, Dec 18, 2008 at 10:44 AM, Thomas Lange - Sun Germany - ham02 -
> Hamburg <[hidden email]> wrote:
>  
>> Hi all,
>>
>> The OOo300 m14 build will feature our latest changes to the grammar
>> checking API and framework. Especially the API should now remain
>> unchanged for the forseeable future. The frame and UI of course will and
>> should still undergo some improvements in the next releases of OOo.
>>
>> Since there were at least one or two changes to the API that required us
>> to become incompatible with grammar checking API used in OOo 3.0 we took
>> the liberty to even make some more changes, usually cleanups and name
>> changes only, to the API as well.
>> With OOo 3.0.1 all the API named XGrammarCheck{er|ing}*.idl is no longer
>> available and replaced with new API files named XProofread{er|ing}*.idl
>>
>>
>> In more detail it looks like this:
>>
>> new API:
>>
>> com/sun/star/text/XMultiTextMarkup
>> com/sun/star/text/TextMarkupDescriptor
>>
>> com/sun/star/linguistic2/ProofreadingIterator
>> com/sun/star/linguistic2/XProofreadingIterator
>>
>> com/sun/star/linguistic2/Proofreader
>> com/sun/star/linguistic2/XProofreader
>> com/sun/star/linguistic2/ProofreadingResult
>> com/sun/star/linguistic2/SingleProofreadingError
>>
>>
>> modified API:
>>
>> com/sun/star/linguistic2/LinguServiceEventFlags
>>  PROOFREAD_AGAIN added
>>
>>
>> If you want to implement a Proofreader (or change your existing grammar
>> checker) for use with OOo 3.0.1 it should be
>> sufficient to read about the last 5 interfaces (starting with
>> Proofreader) only.
>>
>> Of course the OOo minimal version for those new extensions should be OOo
>> 3.0.1.
>>
>>
>> I surely look forward to the see all the new proofreading extensions
>> next year. Especially I hope it will be a rather smooth change for
>> CoGrOO, and Language Tool since those two were already available for OOo
>> 3.0 as extensions and I like to see them with OOo 3.0.1 again. ;-)
>> And thank you so much for all your great work for OOo!
>>
>>
>> Regards,
>> Thomas
>>
>>
>> PS: if you have urgent question about proofreading please drop me a mail
>> as well, since I will be out of the office for the next about 2,5 weeks
>> and not reading this newsgroup in that time. I will have an occasional
>> look at my email account and see if there is sth. coming up that can be
>> answered from out-of-the-office.
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>    
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>  
Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Michel Weimerskirch
Hi

> Adding luxembourgish to Languagetool, is that an option ?
Actually, I've had a look at Languagetool and I have a working
prototype for Luxembourgish (that implements this specific
phonological rule). However, I'd like to have control over the
releases, so I'd prefer to implement it on my own. Also, I do not plan
to implement a full-blown grammar checker, so I think the Languagetool
framework is a bit too large for my needs.

Regards,
Michel

On Thu, Jan 8, 2009 at 5:37 PM, r.j.baars <[hidden email]> wrote:

> Adding luxembourgish to Languagetool, is that an option ?
>
> Ruud
>
> Michel Weimerskirch schreef:
>>
>> Hi
>>
>> Is there a minimalistic Java example available that uses the new API?
>>
>> I am willing to port an old proofreading tool that I wrote for OOo2
>> (that corrects a specific phonological rule in Luxembourgish) to
>> OOo3.0.1, so an example application could help me get started.
>>
>> Regards,
>> Michel
>>
>> On Thu, Dec 18, 2008 at 10:44 AM, Thomas Lange - Sun Germany - ham02 -
>> Hamburg <[hidden email]> wrote:
>>
>>>
>>> Hi all,
>>>
>>> The OOo300 m14 build will feature our latest changes to the grammar
>>> checking API and framework. Especially the API should now remain
>>> unchanged for the forseeable future. The frame and UI of course will and
>>> should still undergo some improvements in the next releases of OOo.
>>>
>>> Since there were at least one or two changes to the API that required us
>>> to become incompatible with grammar checking API used in OOo 3.0 we took
>>> the liberty to even make some more changes, usually cleanups and name
>>> changes only, to the API as well.
>>> With OOo 3.0.1 all the API named XGrammarCheck{er|ing}*.idl is no longer
>>> available and replaced with new API files named XProofread{er|ing}*.idl
>>>
>>>
>>> In more detail it looks like this:
>>>
>>> new API:
>>>
>>> com/sun/star/text/XMultiTextMarkup
>>> com/sun/star/text/TextMarkupDescriptor
>>>
>>> com/sun/star/linguistic2/ProofreadingIterator
>>> com/sun/star/linguistic2/XProofreadingIterator
>>>
>>> com/sun/star/linguistic2/Proofreader
>>> com/sun/star/linguistic2/XProofreader
>>> com/sun/star/linguistic2/ProofreadingResult
>>> com/sun/star/linguistic2/SingleProofreadingError
>>>
>>>
>>> modified API:
>>>
>>> com/sun/star/linguistic2/LinguServiceEventFlags
>>>  PROOFREAD_AGAIN added
>>>
>>>
>>> If you want to implement a Proofreader (or change your existing grammar
>>> checker) for use with OOo 3.0.1 it should be
>>> sufficient to read about the last 5 interfaces (starting with
>>> Proofreader) only.
>>>
>>> Of course the OOo minimal version for those new extensions should be OOo
>>> 3.0.1.
>>>
>>>
>>> I surely look forward to the see all the new proofreading extensions
>>> next year. Especially I hope it will be a rather smooth change for
>>> CoGrOO, and Language Tool since those two were already available for OOo
>>> 3.0 as extensions and I like to see them with OOo 3.0.1 again. ;-)
>>> And thank you so much for all your great work for OOo!
>>>
>>>
>>> Regards,
>>> Thomas
>>>
>>>
>>> PS: if you have urgent question about proofreading please drop me a mail
>>> as well, since I will be out of the office for the next about 2,5 weeks
>>> and not reading this newsgroup in that time. I will have an occasional
>>> look at my email account and see if there is sth. coming up that can be
>>> answered from out-of-the-office.
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Marcin Miłkowski
In reply to this post by Carlos Menezes
CARLOS EDUARDO DANTAS DE MENEZES pisze:

> Thomas,
>
> We are trying to debug new version of CoGrOO (3.0.2) but it sounds a
> bit difficult.
>
> menezes@possante:~$ /opt/broffice.org3/program/soffice -writer
> terminate called after throwing an instance of
> 'com::sun::star::uno::RuntimeException'
> sh: crash_report: not found
>
> Do you have any tip to easy this task?

Did you try debugging the Java code by attaching the debugger as
described here? (I believe CoGrOO was using a small Java interface to
call the standalone CoGrOO installation).

See here:

http://cedric.bosdonnat.free.fr/wordpress/?p=57

This is really a very useful technique - if a grammar checker gets
registered and called (on opening a text document), you will be able to
set breakpoints and get into the code to see what happens. From my
experience, I can tell you that most problems come from not setting the
return values - they are not for fun, they cannot be null, they can be
at most empty.

Regards
Marcin

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

Carlos Menezes
Dear all,

This post explains how to "create a new Remote Java Application":

http://eclipse.dzone.com/articles/how-debug-remote-java-applicat

[]s,

Menezes

2009/1/8 Marcin Miłkowski <[hidden email]>

> CARLOS EDUARDO DANTAS DE MENEZES pisze:
>
>  Thomas,
>>
>> We are trying to debug new version of CoGrOO (3.0.2) but it sounds a
>> bit difficult.
>>
>> menezes@possante:~$ /opt/broffice.org3/program/soffice -writer
>> terminate called after throwing an instance of
>> 'com::sun::star::uno::RuntimeException'
>> sh: crash_report: not found
>>
>> Do you have any tip to easy this task?
>>
>
> Did you try debugging the Java code by attaching the debugger as described
> here? (I believe CoGrOO was using a small Java interface to call the
> standalone CoGrOO installation).
>
> See here:
>
> http://cedric.bosdonnat.free.fr/wordpress/?p=57
>
> This is really a very useful technique - if a grammar checker gets
> registered and called (on opening a text document), you will be able to set
> breakpoints and get into the code to see what happens. From my experience, I
> can tell you that most problems come from not setting the return values -
> they are not for fun, they cannot be null, they can be at most empty.
>
> Regards
> Marcin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: New grammar checking framework available with OOo300 m14

William Colen
In reply to this post by Marcin Miłkowski
Thomas,
I uploaded the extension to
https://sourceforge.net/project/showfiles.php?group_id=182075&package_id=305572
The file is CoGrOO-AddOn-3.0.2-SNAPSHOT-bin.oxt<http://downloads.sourceforge.net/cogroo/CoGrOO-AddOn-3.0.2-SNAPSHOT-bin.oxt?use_mirror=>
Thank you!

Marcin,Thank you! The tutorial helped a lot! I could debug it.

But I still not able to find the crash problem.
Following you can see the logs generated by CoGrOO extension.

My steps to cause the crash was:
1. Created a new document.
2. Changed it to pt_BR
3. Entered a sentence with a grammar error: Fomos levados à crer.
4. Waited a few seconds, no automatic grammar checking (all log entries I
have was generated before I press F7)
5. Pressed F7 -> OOo crashed

The log is clear and easy to read. Something interesting is that the
method doProofreading was never called: no traces from that method and also
I inserted a breakpoint at the method's first line, and Eclipse never
stopped there.

Please help!

Thank you,
William

The log:
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
__getComponentFactory
FINER: ENTRY br.usp.pcs.lta.cogroo.ooointegration.Main
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getServiceNames
FINER: ENTRY
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getServiceNames
FINER: RETURN [com.sun.star.linguistic2.Proofreader,
br.usp.pcs.lta.cogroo.ooointegration.Main]
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
__getComponentFactory
FINER: RETURN com.sun.star.lib.uno.helper.Factory@dd20f6
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main Main
FINER: ENTRY com.sun.star.bridges.jni_uno.JNI_proxy@e7b241[oid=29a296c;msci:unsafe[0];ea3c9e0959d4549984f4eb7f26c9c9f,
type=com.sun.star.uno.XComponentContext]
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main <init>
FINE: Called br.usp.pcs.lta.cogroo.ooointegration.Main
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main <init>
FINE: Will call Resources.init
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main Main
FINER: RETURN
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getImplementationName
FINER: ENTRY
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getImplementationName
FINER: RETURN br.usp.pcs.lta.cogroo.ooointegration.Main
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main getLocales
FINER: ENTRY
Jan 8, 2009 11:04:37 PM br.usp.pcs.lta.cogroo.ooointegration.Main getLocales
FINER: RETURN pt_BR;
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main Main
FINER: ENTRY com.sun.star.bridges.jni_uno.JNI_proxy@e7b241[oid=29a296c;msci:unsafe[0];ea3c9e0959d4549984f4eb7f26c9c9f,
type=com.sun.star.uno.XComponentContext]
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main <init>
FINE: Called br.usp.pcs.lta.cogroo.ooointegration.Main
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main <init>
FINE: Will call Resources.init
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main Main
FINER: RETURN
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getImplementationName
FINER: ENTRY
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main
getImplementationName
FINER: RETURN br.usp.pcs.lta.cogroo.ooointegration.Main
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main getLocales
FINER: ENTRY
Jan 8, 2009 11:04:55 PM br.usp.pcs.lta.cogroo.ooointegration.Main getLocales
FINER: RETURN pt_BR;

Thank you!William


On Thu, Jan 8, 2009 at 3:43 PM, Marcin Miłkowski <[hidden email]> wrote:

> CARLOS EDUARDO DANTAS DE MENEZES pisze:
>
>  Thomas,
>>
>> We are trying to debug new version of CoGrOO (3.0.2) but it sounds a
>> bit difficult.
>>
>> menezes@possante:~$ /opt/broffice.org3/program/soffice -writer
>> terminate called after throwing an instance of
>> 'com::sun::star::uno::RuntimeException'
>> sh: crash_report: not found
>>
>> Do you have any tip to easy this task?
>>
>
> Did you try debugging the Java code by attaching the debugger as described
> here? (I believe CoGrOO was using a small Java interface to call the
> standalone CoGrOO installation).
>
> See here:
>
> http://cedric.bosdonnat.free.fr/wordpress/?p=57
>
> This is really a very useful technique - if a grammar checker gets
> registered and called (on opening a text document), you will be able to set
> breakpoints and get into the code to see what happens. From my experience, I
> can tell you that most problems come from not setting the return values -
> they are not for fun, they cannot be null, they can be at most empty.
>
> Regards
> Marcin
>
12