Jan Nylund | 5 Aug 2008 12:18
Picon

OS X: Can not paste text as filename into save dialog.

Hello!

We just noticed that in both oxygen 9.2 and 9.3 it's not possible to  
paste text as the filename into a save dialog. Pasted text will  
instead appear in the document where you had the cursor placed before  
opening the save dialog.

This may appear in other versions as well, we only tested what we had  
available.

Br,
Jan

--
Jan Nylund
Senior System Designer
Citec Information Oy Ab

Attachment (smime.p7s): application/pkcs7-signature, 1586 bytes
_______________________________________________
oXygen-user mailing list
oXygen-user@...
http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Sorin Ristache | 5 Aug 2008 17:03
Favicon

Re: OS X: Can not paste text as filename into save dialog.

Hello,

The Copy, Cut and Paste actions do not work in the Save dialog of a Mac 
application. You must select the file from the file list of the dialog 
or type the file name. However we were not aware that the actions modify 
the editor panel when the Save dialog which is a modal dialog is 
displayed. We will fix that.

Thank you for reporting the problem,
Sorin

Jan Nylund wrote:
> Hello!
> 
> We just noticed that in both oxygen 9.2 and 9.3 it's not possible to 
> paste text as the filename into a save dialog. Pasted text will instead 
> appear in the document where you had the cursor placed before opening 
> the save dialog.
> 
> This may appear in other versions as well, we only tested what we had 
> available.
> 
> Br,
> Jan
Jan Nylund | 6 Aug 2008 07:30
Picon

Re: OS X: Can not paste text as filename into save dialog.

Hello!

On 5 aug 2008, at 18.03, Sorin Ristache wrote:
> The Copy, Cut and Paste actions do not work in the Save dialog of a  
> Mac application. You must select the file from the file list of the  
> dialog or type the file name. However we were not aware that the  
> actions modify the editor panel when the Save dialog which is a  
> modal dialog is displayed. We will fix that.

Is this related to Save dialogs from Java applications? In regular Mac  
applications I can freely copy, cut and paste the text of the filename  
(tested several, bot apple's and third party softwares).

Br,
Jan

--
Jan Nylund
Senior System Designer
Citec Information Oy Ab

Attachment (smime.p7s): application/pkcs7-signature, 1586 bytes
_______________________________________________
oXygen-user mailing list
oXygen-user@...
http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Sorin Ristache | 6 Aug 2008 10:37
Favicon

Re: OS X: Can not paste text as filename into save dialog

Hello,

Yes, it is a problem of the native Save dialog in the Apple JVM. The 
menu actions are still active when the modal dialog for Save is on 
screen and the keystroke event is passed to the Paste menu action which 
runs on the editor panel. We disabled the actions in the Edit menu when 
the Save dialog is on screen but the keystroke has no effect in this case.

You can use the Paste action in the Save dialog on a Mac computer only 
with a Ctrl + click on the text field and the selection of the Paste 
action in the popup menu.

Regards,
Sorin

Jan Nylund wrote:
> Hello!
> 
> On 5 aug 2008, at 18.03, Sorin Ristache wrote:
>> The Copy, Cut and Paste actions do not work in the Save dialog of a 
>> Mac application. You must select the file from the file list of the 
>> dialog or type the file name. However we were not aware that the 
>> actions modify the editor panel when the Save dialog which is a modal 
>> dialog is displayed. We will fix that.
> 
> 
> Is this related to Save dialogs from Java applications? In regular Mac 
> applications I can freely copy, cut and paste the text of the filename 
> (tested several, bot apple's and third party softwares).
> 
(Continue reading)

Jing, Jenny | 8 Aug 2008 05:21
Favicon

Failed to read schema document

Hi,

I'm trying to set up eXist to validate records with schema. But I keep getting error message when
I tried to save a record in eXist.

Cannot save the file. org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema
document 'file:/export/home/library/eXist/webapp//WEB-INF/entities/works.xsd', because 1)
could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.

Does anyone know what might cause this error message?
The schema's root is <xsd:schema> I am sure about that.

Thanks.

Jenny
Sorin Ristache | 8 Aug 2008 14:13
Favicon

Re: Failed to read schema document

Hello,

I get this error when the schema used for validation cannot be found at
the location specified in the XML document. In your case if there is a
works.xsd file on the hard disk and the root element of the works.xsd
file is xsd:schema the location is not specified correctly in the XML
document. Does works.xsd exist in the directory specified in the XML
document that you try to add to eXist?

/export/home/library/eXist/webapp/WEB-INF/entities/works.xsd

If it exists what is the version of your eXist server?

Regards,
Sorin

Jing, Jenny wrote:
> Hi,
> 
> I'm trying to set up eXist to validate records with schema. But I keep getting error message when
> I tried to save a record in eXist.
> 
> Cannot save the file. org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema
document 'file:/export/home/library/eXist/webapp//WEB-INF/entities/works.xsd', because 1)
could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
> 
> Does anyone know what might cause this error message?
> The schema's root is <xsd:schema> I am sure about that.
> 
> Thanks.
(Continue reading)

Jing, Jenny | 8 Aug 2008 20:13
Favicon

Re: Failed to read schema document

Hi, Sorin:

We use eXist 1.2.3. I set up the config.xml validation=yes.
I also copied our schema files into this folder:  \eXist\webapp\WEB-INF\entities
Then I add the name and uri in the catalog.xml:

 ( I just added the three lines of our own schemas in the <uri name= > in the default catalog.xml.)
Catalog.xml
<!-- $Id: catalog.xml 6282 2007-07-23 18:49:56Z dizzzz $ --> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
    <uri name="http://www.w3.org/XML/1998/namespace" uri="entities/xml.xsd"/>
        <uri name="http://www.w3.org/2001/XMLSchema" uri="entities/XMLSchema.xsd"/>

    <uri name="http://localhost:8080/exist/db/Test/common/schemas/work" uri="entities/works.xsd"/>
    <uri name="http://localhost:8080/exist/db/Test/common/schemas/about" uri="entities/about.xsd"/>
    <uri name="http://localhost:8080/exist/db/Test/common/schemas/common" uri="entities/common.xsd"/>
   <uri name="urn:oasis:names:tc:entity:xmlns:xml:catalog" uri="entities/catalog.xsd" /> </catalog>

This is how I define in our xml record:
<work xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns="http://localhost:8080/exist/db/Test/common/schemas/work">
</work>

But the setting doesn't seem work because the records are not validated by the schema at all.
For example, if we delete a required field, the record is still validated.
But if I tried to save a record, the error message appears.

I don't know whether it's caused by eXist setting or by Oxygen, or the connection between them.

Any suggestion is welcome!

(Continue reading)

Sorin Ristache | 11 Aug 2008 11:52
Favicon

Re: Re: Failed to read schema document

Hello Jenny,

You can get different validation results when saving the XML file in the 
eXist database and when validating the same XML file in an Oxygen editor 
panel if the two validations are executed against different schemas.

When you save the XML file the eXist server validates the file against 
\eXist\webapp\WEB-INF\entities\works.xsd through the eXist XML catalog 
that maps the namespace 
"http://localhost:8080/exist/db/Test/common/schemas/work" to the schema 
\eXist\webapp\WEB-INF\entities\works.xsd. When you validate the same XML 
file opened in an XML editor panel in Oxygen with the toolbar action 
Validate Document other XML Schema file may be used. Oxygen uses the 
same schema file as the eXist server only if you associate the same 
schema file with the XML file with one of the following:

- the xsi:schemaLocation attribute in the XML file,

- a document type created in Preferences -> Document Type Association,

- an XML catalog set in Preferences -> XML -> XML Catalog.

You can find the schema used in Oxygen with the action Open External 
Schema available on the toolbar Document and on the menu Document -> XML 
Document.

Regards,
Sorin

Jing, Jenny wrote:
(Continue reading)

Philipp Steinkrüger | 14 Aug 2008 16:33
Picon
Favicon

Whitespace Problem

Hello!

i am having a problem with white-spaces in Author mode. Here is what my 
XML document looks like at the problematic passage:

            <p>
                Der
                <choice>
                    <orig>E</orig>
                    <reg>e</reg>
                </choice>
            rwirdigen in
                <choice>
                    <orig>G</orig>
                    <reg>g</reg>
                </choice>
            </p>

Now in Author mode, the linebreaks are transformed into whitespace, so 
that the first part looks like "Der E e rwirdigen in" etc. But i would
like to have it look like "Der Eerwirdigen" etc. <p> has the display 
property: block, <choice>, <orig> and <reg> have display property inline,
and i think that exactly is the problem, because the manual says that if 
the display-property is inline, non-whitespace (which my linebreak is, i 
suppose) are transformed into normal white space.
Is there any way to have oxygen ignore the linebreak?

Thank you very much,
Philipp

(Continue reading)

Sorin Ristache | 14 Aug 2008 17:05
Favicon

Re: Whitespace Problem

Hello,

The whitespaces including line breaks are normalized when the XML 
document is rendered in the Author mode. That means the line breaks 
between <orig>E</orig> and <reg>e</reg>, between <reg>e</reg> and 
</choice>, etc are replaced with a space character. If the Author mode 
removes them without replacing them with a space character then the new 
XML document is not the normalized version of the old one.

The only way to display "Der Eerwirdigen" in the Author mode is to 
remove the whitespaces yourself from the XML document before switching 
to the Author mode:

<p>
     Der
     <choice>
         <orig>E</orig><reg>e</reg></choice>rwirdigen in
     <choice>
     ...

Regards,
Sorin

Philipp Steinkrüger wrote:
> Hello!
> 
> i am having a problem with white-spaces in Author mode. Here is what my 
> XML document looks like at the problematic passage:
> 
>            <p>
(Continue reading)


Gmane