Re: [dev] JAVA storing as ODT Flat XML using SAX

[Mikhail Voitenko]

Hi Vincent,

I assume that using of "com.sun.star.comp.Writer.XMLOasisExporter" 
instead of "com.sun.star.comp.Writer.XMLExporter" would let the ODT XML 
format be used.


Best regards,
Mikhail.

Vincent Spiewak wrote:

Hi all
I want to store an ODT "Flat XML" of the current document.
I tried this code from "SAXEcho" project:



DocumentCollector collector = new DocumentCollector(false);

// get the xmlexportfilter service
XMultiComponentFactory m_xMCF = m_xContext.getServiceManager();

Object xmlExporter = null;

xmlExporter =
m_xMCF.createInstanceWithContext("com.sun.star.comp.Writer.XMLExporter",
m_xContext);

// get the interface of xmlexportfilter service
XFilter xFilter = (XFilter)
UnoRuntime.queryInterface(XFilter.class, xmlExporter);
XExporter xExporter = (XExporter)
UnoRuntime.queryInterface(XExporter.class, xmlExporter);
XInitialization xInitialization =
(XInitialization)
UnoRuntime.queryInterface(XInitialization.class, xmlExporter);

Object args[] = new Object[1];
args[0] = (com.sun.star.xml.sax.XDocumentHandler)
UnoRuntime.queryInterface(
com.sun.star.xml.sax.XDocumentHandler.class, collector);

xInitialization.initialize(args);

// get the Desktop service
Object desktop = m_xMCF.createInstanceWithContext(
"com.sun.star.frame.Desktop", m_xContext);

XDesktop xDesktop = (XDesktop) UnoRuntime.queryInterface(
XDesktop.class, desktop);

// set the xcomponent
xExporter.setSourceDocument(xDesktop.getCurrentComponent());

// start the filter
xFilter.filter(new PropertyValue[0]);

Document root = collector.getDocument();

AdapterNode adapter = new AdapterNode(root, null);

// saving...
FileOutputStream fos = new FileOutputStream(tmpUrl);
DocumentDistributor.setFormatting(false);
DocumentDistributor.parseNode(adapter.getNode(), fos, null);
fos.close();


It works great but give a SXW Flat XML, NOT ODT.
Is there a similar way to export in ODT Flat XML ?
Instead, is there any Java Toolkit like AODL ?


--
- Vincent Spiewak - www.versusoft.com -
--



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] OOBASIC Macro and VB .NET

[Mathias Bauer]

openjack wrote:

> 
> Mathias Bauer wrote:
>> 
>> So to change toolbar states you must intercept the status updating
>> procedure. Unfortunately this is not possible using any Basic, neither
>> OOo nor VB. You have to use a programming language that allows to
>> implement UNO objects (C++, Java, Python).
>> 
> 
> I'm really sorry because MAYBE I'm reading a different suggests... I don't
> know If I'm reading good, but my understanding is that I can't hide
> toolbar's button from VB .NET, but Jurgen said "Everythig you do in the
> macro can be done from VB.Net directly and it is possible to disable
> commands." and I can hide Print and Save button from toolbar with a OOBasic
> macro, as I show in my first post.

You are reading quite well. Your error is the assumption that the OOo
Basic code you presented is the right approach. ;-)

As I said, direct manipulation of toolbar buttons using the toolkit API
is not recommended and won't work reliably as internal status update
processing permanently can override your attempt to force a particular
button status.

>> The only case where you can do this without implementing objects is when
>> you want to disable a certain command *all the time*. This is possible
>> with using a simple configuration file, not code is needed.
>> 
> 
> Anyway, I need to hide or disable some functions, like Print or SaveAs. The
> requirement is to show the content of the ODT file, and don't need to Print
> or Save.

So you can put ".uno:Print", ".uno:PrintDirect", ".uno:Save" and
".uno:SaveAs" into the list of DisabledCommands and they will be
automatically disabled without writing any code. IIRC this should be
described in the Developer's Guide. If not, please ask again.

You can even remove the toolbars completely in case you just want to
"view" a document.

Ciao,
Mathias

-- 
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to "[EMAIL PROTECTED]".
I use it for the OOo lists and only rarely read other mails sent to it.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[dev] shared extensions, which layer ?

[Caolan McNamara]

Where should unopkg add --shared stuff end up in a 3 layer OOo, into the
basis layer or the brand layer ?

C.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[dev] benchmarking multiple versions of OOo

[Andrew Ziem]

Hello,

I benchmarked OpenOffice.org 1.1.5 through 3.0.0 m3 to identify trends, 
and I'm quasi-privately offering the benchmark system and the results to 
you, the experts, before I publish anything.


**Method

  1. I simulate a cold start (this marks the beginning of a "pass").
  2. I use Python to start OpenOffice.org, open a document, scroll
 through it, and save it.
  3. Each iteration captures 5 durations (start, open, scroll, export,
 and close).
  4. I repeat for 5 iterations (each pass has 5 iterations).
  5. I repeat this process (a "pass") a total of 10 times per
 OpenOffice.org version.
  6. I repeat this process (10 "passes") for the next OpenOffice.org
 version

**Results
 1. The latest versions are not the fastest---especially for cold starts. 
 2. Warm application startup is fairly consistent.


 See the spreadsheet for more.

**Thoughts

  1. The cold start simulator is not so good.  The first pass of the
 first iteration is generally the slower than the first iteration
 of the second pass.
  2. So I don't hurt performance, I sleep for 0.10 seconds while
 waiting for OpenOffice.org to start accepting UNO connections, but
 0.10 seconds may be too high because of the small differences in
 warm startup.
  3. I want to add OOo 1.1.0 using a conversion of the .odt test doc to
 .sxw.
  4. OOo 1.1.5 imports the .odt test document, but you could argue it
 should import .sxw?  Also, OOo of course saves to .sxw.

**System
 Hardware made about three years ago
 AMD Athlon XP 3000+ (32-bit single core), ~750MB RAM, PATA disks, 
Fedora 7, Linux 2.6.23
 
http://www.smolts.org/client/show?uuid=pub_c71602de-1592-48e5-8dec-7f5265f4c5c5


**Downloads: Results and code
   You can download the results (spreadsheets with charts and numbers), 
the source code, and the test document at the following address. The 
system is a bit messy, so the code is not officially released.  :)  The 
interesting parts of the results are in >in the sheets cold_start and warm_start.  If you dare run the program, 
please read the README.txt first.


http://katana.oooninja.com/f/ref/ODF_text_reference_v1.odt <-- reference 
document
http://katana.oooninja.com/f/tmp/benchmark-ooo-2008-04-07-08-25.tar.bz2 
<-- results and code



Andrew

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[dev] Re: [OOoCon2008] Possible need to postpone the OOoCon (November 5 to 7)

[pj @ OOo]

Dear OOo community,

after evaluating the pros and cons of several possible dates to hold the 
OOoCon, we are now planning to welcome you to Beijing from November 5 to 7.


The main reason to eye November is the fact, that flight prices normally 
drop significantly after October. Another important reason for us is, 
that we are quite sure, that OOo 3.0 can be celebrated at the OOoCon.


I just want to ask for another round of complaints about this newly 
proposed dates. If nobody gives an significant issue against holding the 
OOoCon from November 5 to 7, we will announce this dates as final by the 
end of this week.


Best regards,
Peter

pj @ OOo wrote:

Dear OOo Community,

so far, we were sure, that the chosen dates for the OOoCon, October 15 
to 17, doesn't cause any significant problem for almost anybody willing 
to attend. Recently, we found out, that we have a real big problem. 
Northern Germany has public school holidays from October 13 to 25. Sun's 
engineers, the most active part of the community, all live there. 
Probably a lot of them might be on vacation with their wife and kids at 
that time, being not able to attend the OOoCon. In the moment they are 
evaluating the impact. Consequently, I also want to request comments 
here, what would be obstacles to reschedule. From my point of view, we 
have no option to prepone. The Beijing Paralympics end at September 16 
and in the first week of October, there are Chinese national holidays. 
Our only option is to postpone. My suggestion would be to face October 
29 to 31 as an alternative. Who has any issues against this dating?


I am really sorry about this news.

Best regards,
Peter



--
Peter Junge

OpenOffice.org Annual Conference
Beijing 2008
Organizational Team

I want *YOU* to come to Beijing!

Visa information:
http://wiki.services.openoffice.org/wiki/OOoCon_2008_Visa_Procedures

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[dev] Re: [tools-perf] Re: [dev] Benchmarking multiple versions of OOo

[Michael Meeks]

On Mon, 2008-04-07 at 14:40 -0600, Andrew Z wrote:
> > What I really want is something like Michael's
> > http://live.gnome.org/iogrind but that just says "your app burned up
> > 110,000 bogoios and 90,000,000 bogocpus" and every time you run it it
> > says "110,000 bogoios and 90,000,000 bogocups". It doesn't even matter
> > too much if it the ratio is wildly different to the real world as long
> > as it's consistent between runs and reducing measurable bogoios reduces
> > real world work by some amount.
> 
> I am not a performance guru, but I think not all bogoios are worth the
> same in practice.  For example, see slides 15-16 here

So - bogoio's are the right approach; the problem is less getting an
accurate simulation, but getting a repeatable simulation :-) of course,
accuracy is nice if you can be repeatable; but ...

Unfortunately, iogrind doesn't work wonderfully well for threaded
applications; but it can be run on OO.o to profile cold-start; and it
might even give some useful numbers - particularly now there is a
'warming' feature (so you can simulate eg. gedit first to warm the gtk
+ / glibc stack (etc.)).

The console mode will give you a single "12.35 bogoseconds" type
number.

HTH,

Michael.

-- 
 [EMAIL PROTECTED]  <><, Pseudo Engineer, itinerant idiot



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] shared extensions, which layer ?

[Stephan Bergmann]

Caolan McNamara wrote:

Where should unopkg add --shared stuff end up in a 3 layer OOo, into the
basis layer or the brand layer ?


Shared extensions go into the brand layer.  Quoting 
:


*  The share/extension/install directory can contain brand specific 
Extensions that are deployed shared at installation time.
* This implies that the shared Extension layer (share/uno_packages) is 
in the Brand layer, not the OOo-Basis layer. (TODO: a future extension 
might be to add a third Extension layer in the OOo-Basis layer.)


-Stephan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] Re: [OOoCon2008] Possible need to postpone the OOoCon (November 5 to 7)

[Charles-H. Schulz]

Le 8 avr. 08 à 08:37, Maho NAKATA a écrit :

From: "pj @ OOo" <[EMAIL PROTECTED]>
Subject: Re: [OOoCon2008] Possible need to postpone the OOoCon  
(November 5 to 7)

Date: Tue, 08 Apr 2008 13:55:59 +0800


Dear OOo community,

after evaluating the pros and cons of several possible dates to  
hold the
OOoCon, we are now planning to welcome you to Beijing from November  
5 to 7.


The main reason to eye November is the fact, that flight prices  
normally

drop significantly after October. Another important reason for us is,
that we are quite sure, that OOo 3.0 can be celebrated at the OOoCon.


Just +1
better for me :)



It turns out to be indeed a convenient date. The only question that  
comes to my mind is what's the weather like in November (and please  
don't answer "polluted").


Best,

Charles.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] shared extensions, which layer ?

[Caolan McNamara]

On Tue, 2008-04-08 at 15:20 +0200, Stephan Bergmann wrote:
> Caolan McNamara wrote:
> > Where should unopkg add --shared stuff end up in a 3 layer OOo, into the
> > basis layer or the brand layer ?
> 
> Shared extensions go into the brand layer.  Quoting 
> :
> 
> *  The share/extension/install directory can contain brand specific 
> Extensions that are deployed shared at installation time.
> * This implies that the shared Extension layer (share/uno_packages) is 
> in the Brand layer, not the OOo-Basis layer. (TODO: a future extension 
> might be to add a third Extension layer in the OOo-Basis layer.)

I guess if I wanted to e.g. share them between two optionally available
brands right now I could simply try and link the two uno_packages dir to
some single location. Just kicking around packaging the BrOffice.org
brand in additional to the stock OOo brand, and want to try and keep
things simple wrt. the existing packaged extensions and upgrade paths.

Also (for the moment at least) if someone has extensions installed under
OOo2 systemwide they won't be migrated automagically to OOo3 as the
locations are different now. I note that if I simply move the OOo2
uno_packages dir into OOo3 that it "works", anyone know if I have any
sort of guarantee that it "should work" ?

C.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] JAVA storing as ODT Flat XML using SAX

[Vincent Spiewak]

Thanks mikhall, it works !

I wrote a Java Class converting ODT to FlatXML using DOM in the meantime.
See bellow:

package com.versusoft.packages.ooo;

import java.io.ByteArrayInputStream;
import java.io.File;
import java.io.IOException;
import java.util.zip.ZipEntry;
import java.util.zip.ZipFile;
import javax.xml.parsers.ParserConfigurationException;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.TransformerException;
import org.w3c.dom.Element;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.OutputKeys;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.stream.StreamResult;
import org.w3c.dom.Document;
import org.w3c.dom.DocumentFragment;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.xml.sax.EntityResolver;
import org.xml.sax.InputSource;
import org.xml.sax.SAXException;

/**
 *
 * @author vince
 */
public class OdtUtils {

public static void ODTtoFlatXML(String fileIn, String fileOut) throws
IOException, ParserConfigurationException, SAXException,
TransformerConfigurationException, TransformerException {
ZipFile zf = null;

zf = new ZipFile(fileIn);

ZipEntry metaEntry = zf.getEntry("meta.xml");
ZipEntry stylesEntry = zf.getEntry("styles.xml");
ZipEntry contentEntry = zf.getEntry("content.xml");
ZipEntry settingsEntry = zf.getEntry("settings.xml");

DocumentBuilderFactory docFactory =
DocumentBuilderFactory.newInstance();
docFactory.setValidating(false);

DocumentBuilder docBuilder = docFactory.newDocumentBuilder();
docBuilder.setEntityResolver(new EntityResolver() {

public InputSource resolveEntity(java.lang.String publicId,
java.lang.String systemId)
throws SAXException, java.io.IOException {

return new InputSource(new ByteArrayInputStream("".getBytes()));

}
});


Document doc = docBuilder.newDocument();
Element racine = doc.createElement("office:document");


Document metaDoc = docBuilder.parse(zf.getInputStream(metaEntry));
Document stylesDoc =
docBuilder.parse(zf.getInputStream(stylesEntry));
Document contentDoc =
docBuilder.parse(zf.getInputStream(contentEntry));
Document settingsDoc =
docBuilder.parse(zf.getInputStream(settingsEntry));

String parentPath = new File(fileIn).getParent();
System.out.println("path=" + parentPath);

replaceObjectContent(docBuilder, contentDoc, zf, parentPath);

racine.setAttribute("xmlns:meta",
"urn:oasis:names:tc:opendocument:xmlns:meta:1.0");
racine.setAttribute("xmlns:xsl", "
http://www.w3.org/1999/XSL/Transform";);
racine.setAttribute("xmlns:office",
"urn:oasis:names:tc:opendocument:xmlns:office:1.0");
racine.setAttribute("xmlns:style",
"urn:oasis:names:tc:opendocument:xmlns:style:1.0");
racine.setAttribute("xmlns:text",
"urn:oasis:names:tc:opendocument:xmlns:text:1.0");
racine.setAttribute("xmlns:table",
"urn:oasis:names:tc:opendocument:xmlns:table:1.0");
racine.setAttribute("xmlns:draw",
"urn:oasis:names:tc:opendocument:xmlns:drawing:1.0");
racine.setAttribute("xmlns:fo",
"urn:oasis:names:tc:opendocument:xmlns:xsl-fo-compatible:1.0");
racine.setAttribute("xmlns:meta",
"urn:oasis:names:tc:opendocument:xmlns:meta:1.0");
racine.setAttribute("xmlns:number",
"urn:oasis:names:tc:opendocument:xmlns:datastyle:1.0");
racine.setAttribute("xmlns:svg",
"urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0");
racine.setAttribute("xmlns:chart",
"urn:oasis:names:tc:opendocument:xmlns:chart:1.0");
racine.setAttribute("xmlns:dr3d",
"urn:oasis:names:tc:opendocument:xmlns:dr3d:1.0");
racine.setAttribute("xmlns:form",
"urn:oasis:names:tc:opendocument:xmlns:form:1.0");
racine.setAttribute("xmlns:script",
"urn:oasis:names:tc:opendocument:xmlns:script:1.0");
racine.setAttribute("xmlns:xlink", "http://www.w3.org/1999/xlink";);
racine.setAttribute("xmlns:dc", "http://purl.org/dc/elements/1.1/";);
racine.setAttribute("xmlns:math", "
http://www.w3.org/1998/Math/MathML";);
racine.setAttribute("xmlns:dom", "http://www.w3.org/2001/xml-events
");
racine.setAttribute("xmlns:xforms", "http://www.w3.org/2002/xforms
");
racine.setAttribute("xmlns:xsd", "http://www.w3.org/2001/XMLSchema
");
racine.setAttribute("xmlns:xsi", "
http://www.w3.org/2001/XMLSchema-instance";);
racine.setAttribute("xmlns:config",
"urn:oasis:names:tc:opendocument:xmlns:config:1.0");

NodeList nodelist = metaDoc.getDocumentElement().getChildNodes();
for (int i = 0; i < nodelist.getLength(); i++) {
racine.appendChild(doc.importNode(nodelist.item(i), true));
 

[dev] difficult access debugging symbols

[Terrence Enger]

Greetings,

I have built OOH680_m10 on ubuntu-Gutsy (7.10).  Somewhere between
creation of libraries in the solver and installing from the rpm's, I
lose debugging symbols.

I configured with
--enable-symbols 
and built with
dmake debug=true

The build process produces lines ...
checking whether to strip the solver or not checking whether to
enable native CUPS support... yes
(yes that is one line), and ...
The variable DISABLE_STRIP is set to: TRUE
checking whether stripping libraries is possible... yes
and then only 17 lines apart close to the end of the build ...
make_installer.pl, version 1.0
Stripping files
so I suspect that the loss occurs before the .rpm files are created.
After another configure with --disable-strip-solver, another dmake
debug=true recreated the .rpm files, but they are only very slightly
bigger than before and still the installed files lack debugging
symbols.

I can access the debugging symbols by linking from my installed
directory back to the files built in the solver.  Is there a more
straight-forward way?

Here are some details ...

  The earlier configure command reads, with line-breaks added here for
  readability ...

  ./configure_fudge 
--disable-mozilla --with-stdlibs --with-system-zlib 
--with-system-openssl --with-system-jpeg --with-system-expat 
--with-system-freetype --with-system-libwpd --with-system-python 
--with-system-db --with-system-hsqldb --with-system-beanshell 
--with-system-sml-apis --with-system-xerces --with-system-xalan 
--with-system-libxslt --with-system-odbc-headers 
--with-system-sane-header --with-system-xrender-headers 
--with-system-curl --with-system-boost --with-system-vigra 
--with-system-neon --with-system-hunspell --with-system-odbc 
--with-system-sane-header --disable-pasf --without-fonts 
--without-dict --disable-odk --without-myspell-dicts 
--with-package-format=rpm --enable-symbols

  I hacked configure_fudge from configure to accept hsqldb 1.8.0.8
  instead of hsqldb 1.8.0.9 which the distributed configure requires.
  (Well, I guess that in itself is grounds for another question soon.)
  I still have output from the build, but it is really big.  The
  installation script is homebrewed (before I learned about
  unxlngi6.pro/bin/userscripts/install).  The central part, following
  the pattern of OpenOffice.org 2.0 Setup Guide, page 39, is ...

rpm --install \
--dbpath $RPMDB \
--nodeps \
--prefix $DESTDIR \

~/OOo_hacking/${WHAT}/instsetoo_native/unxlngi6.pro/OpenOffice/rpm/install/e
n-US/RPMS/*.rpm

I must presume that I am missing something really obvious.  Thank you
for your attention.

Terry.




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] difficult access debugging symbols

[Rüdiger Timm]

Terrence Enger schrieb:

Greetings,

I have built OOH680_m10 on ubuntu-Gutsy (7.10).  Somewhere between
creation of libraries in the solver and installing from the rpm's, I
lose debugging symbols.


I think libraries get stripped during deliver. That means, in your 
module output trees (e.g. sw/unxlngi6.pro/lib) you should have files 
with symbols, on solver without.


Ruediger




I configured with
--enable-symbols 
and built with

dmake debug=true

The build process produces lines ...
checking whether to strip the solver or not checking whether to
enable native CUPS support... yes
(yes that is one line), and ...
The variable DISABLE_STRIP is set to: TRUE
checking whether stripping libraries is possible... yes
and then only 17 lines apart close to the end of the build ...
make_installer.pl, version 1.0
Stripping files
so I suspect that the loss occurs before the .rpm files are created.
After another configure with --disable-strip-solver, another dmake
debug=true recreated the .rpm files, but they are only very slightly
bigger than before and still the installed files lack debugging
symbols.

I can access the debugging symbols by linking from my installed
directory back to the files built in the solver.  Is there a more
straight-forward way?

Here are some details ...

  The earlier configure command reads, with line-breaks added here for
  readability ...

  ./configure_fudge 
--disable-mozilla --with-stdlibs --with-system-zlib 
--with-system-openssl --with-system-jpeg --with-system-expat 
--with-system-freetype --with-system-libwpd --with-system-python 
--with-system-db --with-system-hsqldb --with-system-beanshell 
--with-system-sml-apis --with-system-xerces --with-system-xalan 
--with-system-libxslt --with-system-odbc-headers 
--with-system-sane-header --with-system-xrender-headers 
--with-system-curl --with-system-boost --with-system-vigra 
--with-system-neon --with-system-hunspell --with-system-odbc 
--with-system-sane-header --disable-pasf --without-fonts 
--without-dict --disable-odk --without-myspell-dicts 
--with-package-format=rpm --enable-symbols


  I hacked configure_fudge from configure to accept hsqldb 1.8.0.8
  instead of hsqldb 1.8.0.9 which the distributed configure requires.
  (Well, I guess that in itself is grounds for another question soon.)
  I still have output from the build, but it is really big.  The
  installation script is homebrewed (before I learned about
  unxlngi6.pro/bin/userscripts/install).  The central part, following
  the pattern of OpenOffice.org 2.0 Setup Guide, page 39, is ...

rpm --install \
--dbpath $RPMDB \
--nodeps \
--prefix $DESTDIR \

~/OOo_hacking/${WHAT}/instsetoo_native/unxlngi6.pro/OpenOffice/rpm/install/e
n-US/RPMS/*.rpm

I must presume that I am missing something really obvious.  Thank you
for your attention.

Terry.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[dev] Wrong panel size of Docconverter and Euroconverter Wizards

[KAMI]

Hi!

My Document converter and Euro Converter (from File - Wizards) has wrong
panel size. The panel is smaller than in general. Do you happen to know
what causes this kind of malfunction? Please check the attached image.
It shows the size of the wizard with Hungarian interface. I checked the
macro in it but is shows a normal size of panel. Do you have idea what
goes wrong?


KAMI



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]