Skip to main content

Again - encoding of spanish resources

29 replies [Last post]
Anonymous

Diego,

just grabbed your spanish resource files from the incubator - looks like
something went wrong, though. I'll attach a screenshot of how the find
dialog looks if I switch to Locale.setDefault(new Locale("es", "", "").

Any idea what happened?

Thanks
Jeanette

[search_es.png]
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Kleopatra

Hi Daniel,

>
> True. It would probably require a custom ResourceBundle implementation. If
> the JDNC/SwingX team agrees to switch to UTF8 XML properties as a standard,
> I would be willing to write this (it would be pretty straight forward.) It
> would be a good addition to Java 6 anyway, and would win the team lots of
> friends in the non-ASCII world :-) The old properties can be converted
> programmatically.
>

Sounds great, the new ResourceBundle implementation could be made to
handle old-style properties as well, right? Thumbs up from Berlin, go
ahead Could you file an enhancement issue? What would you expect the
timeline for such an implementation would be?

> Death to Unicode escapes,

Jeanette

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Daniel Leuck

Hi Jeanette,

> Sounds great, the new ResourceBundle implementation could be made to
> handle old-style properties as well, right?

Correct.

> Thumbs up from Berlin, go
> ahead Could you file an enhancement issue? What would you expect the
> timeline for such an implementation would be?

A day or so. I'll try and sort it this weekend.

Cheers,
Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

dags
Offline
Joined: 2003-06-10

I commited a sample xml properties file, swingx_xml_es.properties, in jdnc-incubator (dags/java/org/jdesktop/swingx/plaf/resources/swingx_xml_es.properties)
which can be used to test new implementation.

[code]

Coincidencia de mayúsculas/minúsculas
contiene
igual
termina con
empieza con

Búsqueda Circular
Hacia Atrás
Buscar
Cerrar
Buscar Siguiente
Buscar Anterior
Buscar
B
Buscar

Cerrar
Cancelar
Aceptar

Desplazamiento Horizontal
Compactar Todas las Columnas
Compactar la Columna Seleccionada

Cortar
Copiar
Pegar
Eliminar
Seleccionar Todo

Arriba
Abajo
Desplazar hacia Arriba
Página Arriba
Desplazar hacia Abajo
Página Abajo

Borde Izquierdo
Borde Derecho
Desplazar a la Izquierda
Página Izquierda
Desplazar a la Derecha
Página Derecha

[/code]
Regards,
Diego.

Daniel Leuck

Hi Jeanette,

> ... that doesn't look so good (didn't test, only skimmed the sources, so
> hopefully I missed something :) - ResourceBundle.getBundle() ultimately
> calls new PropertyResourceBundle(stream) which in turn uses the
> properties.load(stream). Hmmm...

True. It would probably require a custom ResourceBundle implementation. If
the JDNC/SwingX team agrees to switch to UTF8 XML properties as a standard,
I would be willing to write this (it would be pretty straight forward.) It
would be a good addition to Java 6 anyway, and would win the team lots of
friends in the non-ASCII world :-) The old properties can be converted
programmatically.

Death to Unicode escapes,
Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

rbair
Offline
Joined: 2003-07-08

> True. It would probably require a custom
> ResourceBundle implementation. If
> the JDNC/SwingX team agrees to switch to UTF8 XML
> properties as a standard,
> I would be willing to write this (it would be pretty
> straight forward.) It
> would be a good addition to Java 6 anyway, and would
> win the team lots of
> friends in the non-ASCII world :-) The old
> properties can be converted
> programmatically.

Personally, I think it's a great idea. From this thread I don't see any downsides other than slightly more complex ResourceBundle loading.

Richard

Kleopatra

Daniel Leuck wrote:
> Actually, its not a very good idea to have a bunch of properties files in
> Unicode escape sitting around. The whole point of a properties file is that
> it is easy to read and edit. At Ikayzo (which is a localization company
> among other things) we have banned use of the regular properties format for
> this reason. There is nothing more frustrating than trying to make a quick
> fix to a properties file and discovering you can't read the file even though
> you speak the language!
>

agreed.

> I would suggest using the new XML properties format (UTF8 encoding)
> introduced with Java 5,

interesting - wasn't aware that there is such a beast (shame on me!).
Could you guide me a bit closer to where to look for it?

The reason we are using resourceBundles is that they have are easily
integratable into the UIManager - we can add them and forget about their
existence, the UIManager will do all the lookup with a reasonable
default strategy.

Jeanette

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Daniel Leuck

Hi Jeanette,

> > I would suggest using the new XML properties format (UTF8 encoding)
> > introduced with Java 5,
>
> interesting - wasn't aware that there is such a beast (shame on me!).
> Could you guide me a bit closer to where to look for it?

Sure. I think most people missed it because it was quietly added to the
regular java.util.Properties class. The XML format is described in the
JavaDocs:

http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html

> The reason we are using resourceBundles is that they have are easily
> integratable into the UIManager - we can add them and forget about their
> existence, the UIManager will do all the lookup with a reasonable
> default strategy.

XML properties should work with ResourceBundles. We use SDL because its
less verbose (I wrote it before the XML properties came about), but I
understand you want to stick with the JDK :-)

Cheers,
Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Kleopatra

Hi Daniel,
>
> Sure. I think most people missed it because it was quietly added to the
> regular java.util.Properties class. The XML format is described in the
> JavaDocs:
>
> http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html
>
>

thanks, looks good only...

>
> XML properties should work with ResourceBundles.

... that doesn't look so good (didn't test, only skimmed the sources, so
hopefully I missed something :) - ResourceBundle.getBundle() ultimately
calls new PropertyResourceBundle(stream) which in turn uses the
properties.load(stream). Hmmm...

> We use SDL because its
> less verbose (I wrote it before the XML properties came about), but I
> understand you want to stick with the JDK :-)
>

I have to ;-)

Thanks
Jeanette

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

dags
Offline
Joined: 2003-06-10

I found an article:

Taming Tiger: Loading Properties from XML

with these note :

[b]A note about resource bundles[/b]
While the java.util.Properties class now supports properties files as XML files in addition to key-value pairs, unfortunately, there is no built-in option available to treat a ResourceBundle as an XML file. Yes, a PropertyResourceBundle does use a Properties object to load the bundle; however, the use of the load method is hard-coded into the class, and the newer loadFromXML()
method is not used.

Regards,
Diego.

Kleopatra

jdnc-interest@javadesktop.org wrote:
> I found an article:
>
> Taming Tiger: Loading Properties from XML
>
> with these note :
>
> [b]A note about resource bundles[/b]
> While the java.util.Properties class now supports properties files as XML files in addition to key-value pairs, unfortunately, there is no built-in option available to treat a ResourceBundle as an XML file. Yes, a PropertyResourceBundle does use a Properties object to load the bundle; however, the use of the load method is hard-coded into the class, and the newer loadFromXML()
> method is not used.
>

aaaaarrrgggghhh.... thanks for the pointer. I'll add it to my favourite
nag about java over the years: add a useful feature to one jdk version
and then wait one to two versions until it is used internally! Hint,
hint to anybody from the core teams listening in ...

Jeanette

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Daniel Leuck

Hi Jeanette and Diego,

I'm on the Java 6 expert group. If we add this to SwingX, I can push for
its inclusion in the platform.

Dan

> -----Original Message-----
> From: Kleopatra [mailto:fastegal@swingempire.de]
> Sent: Wednesday, October 19, 2005 5:49 AM
> To: jdnc@jdnc.dev.java.net
> Subject: Re: Again - encoding of spanish resources
>
> jdnc-interest@javadesktop.org wrote:
> > I found an article:
> >
> > Taming Tiger: Loading Properties from XML
> >
> > with these note :
> >
> > [b]A note about resource bundles[/b]
> > While the java.util.Properties class now supports properties files as
> XML files in addition to key-value pairs, unfortunately, there is no
> built-in option available to treat a ResourceBundle as an XML file. Yes, a
> PropertyResourceBundle does use a Properties object to load the bundle;
> however, the use of the load method is hard-coded into the class, and the
> newer loadFromXML()
> > method is not used.
> >
>
> aaaaarrrgggghhh.... thanks for the pointer. I'll add it to my favourite
> nag about java over the years: add a useful feature to one jdk version
> and then wait one to two versions until it is used internally! Hint,
> hint to anybody from the core teams listening in ...
>
> Jeanette
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
> For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

dags
Offline
Joined: 2003-06-10

Dan:

It is OK for me but remember: I am only the translator.

There is any java tool to work with these XML files ?. While it is easier to read (no escaped unicode!) I guess that it will be harder to edit without a proper tool.

In former properties files, syntax and formatting are simpler than XML files.

Regards,
Diego.

Daniel Leuck

Hi Diego,

> It is OK for me but remember: I am only the translator.

I realize this. That is why I posted it here and not in a private email.
The JDNC/SwingX folks can agree, or tell me to bugger off :-)

> There is any java tool to work with these XML files ?.
> While it is easier
> to read (no escaped unicode!) I guess that it will be harder to edit
> without a proper tool.

You don't need a special tool. All modern text editors and IDEs support
UTF8. I use jEdit (http://www.jedit.org) and Eclipse. If you have any
trouble working with the files just let me know. I am happy to help.

> In former properties files, syntax and formatting are simpler than XML
> files.

True, which is why I wrote SDL (http://sdl.ikayzo.org), but for now XML
property files is probably an easier sell. The XML format used for the
properties files is pretty simple as DTDs/schemas go.

Cheers,
Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

dags
Offline
Joined: 2003-06-10

I use jedit too. My concern was about XML formatting issues but I guess there should be some "xml enabled" editor or jedit plugin to solve that.

Regards,
Diego.

dags
Offline
Joined: 2003-06-10

I found that Mustang seems to have the XML issue solved, or sort of, with ResourceBundle.Control.

Maybe that functionality could be implemented in 5.0 ?.

Please see:

http://download.java.net/jdk6/docs/api/java/util/ResourceBundle.Control....

An example from Mustang docs :

[b]The following is an example of loading XML-based bundles using Properties.loadFromXML.[/b]
[code]
ResourceBundle rb = ResourceBundle.getBundle("Messages",
new ResourceBundle.Control() {

public List getFormats(String baseName) {
if (baseName == null)
throw new NullPointerException();
return Arrays.asList("xml");
}

public ResourceBundle newBundle(String baseName,
Locale locale,
String format,
ClassLoader loader,
boolean reload)
throws IllegalAccessException,
InstantiationException,
IOException {
if (baseName == null || locale == null
|| format == null || loader == null)
throw new NullPointerException();
ResourceBundle bundle = null;
if (format.equals("xml")) {
String bundleName = toBundleName(baseName, locale);
String resourceName = toResourceName(bundleName, format);
InputStream stream = null;
if (reload) {
URL url = loader.getResource(resourceName);
if (url != null) {
URLConnection connection = url.openConnection();
if (connection != null) {
// Disable caches to get fresh data for
// reloading.
connection.setUseCaches(false);
stream = connection.getInputStream();
}
}
} else {
stream = loader.getResourceAsStream(resourceName);
}
if (stream != null) {
BufferedInputStream bis = new BufferedInputStream(stream);
bundle = new XMLResourceBundle(bis);
bis.close();
}
}
return bundle;
}
});

...

private static class XMLResourceBundle extends ResourceBundle {
private Properties props;
XMLResourceBundle(InputStream stream) throws IOException {
props = new Properties();
props.loadFromXML(stream);
}
protected Object handleGetObject(String key) {
return props.getProperty(key);
}
public Enumeration getKeys() {
...
}
}

[/code]

Regards,
Diego.

Daniel Leuck

Hi Diego,


I somehow missed this.

Thank you for pointing it out. I'll take a look. I'm sure we could
back-port it.

Dan

> -----Original Message-----
> From: jdnc-interest@javadesktop.org [mailto:jdnc-interest@javadesktop.org]
> Sent: Wednesday, October 19, 2005 1:10 PM
> To: jdnc@jdnc.dev.java.net
> Subject: Re: RE: RE: Again - encoding of spanish resources
>
> I found that Mustang seems to have the XML issue solved, or sort of, with
> ResourceBundle.Control.
>
> Maybe that functionality could be implemented in 5.0 ?.
>
> Please see:
>
> http://download.java.net/jdk6/docs/api/java/util/ResourceBundle.Control.ht
> ml
>
> An example from Mustang docs :
>
> [b]The following is an example of loading XML-based bundles using
> Properties.loadFromXML.[/b]
> [code]
> ResourceBundle rb = ResourceBundle.getBundle("Messages",
> new ResourceBundle.Control() {
>
> public List getFormats(String baseName) {
> if (baseName == null)
> throw new NullPointerException();
> return Arrays.asList("xml");
> }
>
> public ResourceBundle newBundle(String baseName,
> Locale locale,
> String format,
> ClassLoader loader,
> boolean reload)
> throws IllegalAccessException,
> InstantiationException,
> IOException {
> if (baseName == null || locale == null
> || format == null || loader == null)
> throw new NullPointerException();
> ResourceBundle bundle = null;
> if (format.equals("xml")) {
> String bundleName = toBundleName(baseName, locale);
> String resourceName = toResourceName(bundleName, format);
> InputStream stream = null;
> if (reload) {
> URL url = loader.getResource(resourceName);
> if (url != null) {
> URLConnection connection = url.openConnection();
> if (connection != null) {
> // Disable caches to get fresh data for
> // reloading.
> connection.setUseCaches(false);
> stream = connection.getInputStream();
> }
> }
> } else {
> stream = loader.getResourceAsStream(resourceName);
> }
> if (stream != null) {
> BufferedInputStream bis = new
> BufferedInputStream(stream);
> bundle = new XMLResourceBundle(bis);
> bis.close();
> }
> }
> return bundle;
> }
> });
>
> ...
>
> private static class XMLResourceBundle extends ResourceBundle {
> private Properties props;
> XMLResourceBundle(InputStream stream) throws IOException {
> props = new Properties();
> props.loadFromXML(stream);
> }
> protected Object handleGetObject(String key) {
> return props.getProperty(key);
> }
> public Enumeration getKeys() {
> ...
> }
> }
>
> [/code]
>
> Regards,
> Diego.
> ---
> [Message sent by forum member 'dags' (Diego Gil)]
>
> http://www.javadesktop.org/forums/thread.jspa?messageID=120545
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
> For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

dags
Offline
Joined: 2003-06-10

Please be aware that there is an open bug related to properties.dtd.

I was using jedit's XML plugin and get some validation errors. Anyway, jedit does a good job.

here is bug link:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6277868

Regards,
Diego.

Daniel Leuck

Actually, its not a very good idea to have a bunch of properties files in
Unicode escape sitting around. The whole point of a properties file is that
it is easy to read and edit. At Ikayzo (which is a localization company
among other things) we have banned use of the regular properties format for
this reason. There is nothing more frustrating than trying to make a quick
fix to a properties file and discovering you can't read the file even though
you speak the language!

I would suggest using the new XML properties format (UTF8 encoding)
introduced with Java 5, or some other simple UTF8 enabled properties format
such as SDL (http://sdl.ikayzo.org). Either approach will remove encoding
concerns and make it easy to edit and read properties in any language
regardless of your default locale.

Dan

> -----Original Message-----
> From: jdnc-interest@javadesktop.org [mailto:jdnc-interest@javadesktop.org]
> Sent: Thursday, October 13, 2005 4:00 AM
> To: jdnc@jdnc.dev.java.net
> Subject: Re: Again - encoding of spanish resources
>
> Jeanette:
>
> I checked swingx_de.properties (in swingx project) and seems that has not
> been processed with native2ascii. That confuses me! :-). Properties files
> must be processed with native2ascii or not ?.
>
> Regards,
> Diego.
> ---
> [Message sent by forum member 'dags' (Diego Gil)]
>
> http://www.javadesktop.org/forums/thread.jspa?messageID=119240
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
> For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

dags
Offline
Joined: 2003-06-10

It is OK for me, but I am only the translator.

I guess that should be better to use the new XML properties format, if decided to change.

Regards,
Diego.

dags
Offline
Joined: 2003-06-10

I forget to mention that I am using OmegaT to translate Netbeans properties files. It is a nice program that let you maintain syncronized the original Bundle.properties with Bundle_es.properties, for instance.

It handle all encoding issues, resulting in *_es.properties files with Unicode escapes code when needed.

But the most interesting part is that keep a memory of translated terms, which can be used to make new translations easier.

Netbeans projects keep a list of "translatable files" so translators only need to watch these files. Besides, there is a special project, translatedfiles, where translator can commit their work.

During build process, translated properties files are taken from this project and bundled in main build.

I think that swinglabs should implement something like that if translation work grows.

Regards,
Diego.

Daniel Leuck

Hi Diego,

> I forget to mention that I am using OmegaT to translate Netbeans
> properties files.

OmegaT is a great project. Its nice to have an open source translation
memory tool.

> It is a nice program that let you maintain syncronized
> the original Bundle.properties with Bundle_es.properties, for instance.
> It handle all encoding issues, resulting in *_es.properties files with
> Unicode escapes code when needed.

Unicode escapes are just a bad idea. You may be able to manage with Spanish
encodings because of the large overlap with ASCII, but working with
languages like Russian or Japanese where _all_ the characters are escaped is
a nightmare. You can't read anything or make quick changes without special
tool support. You might as well be using a binary format. The properties
should be in UTF8 XML, SDL, or something similar.

Regards,
Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Kleopatra

jdnc-interest@javadesktop.org wrote:
> Jeanette:
>
> I am looking at swingx_es.properties in jdnc-incubator
> and can't find anything wrong. I used native2ascii as directed.

Hmm ... I'll check again, maybe I did something weird when checking out
(as I mentioned in the follow-up, it#s strange that only the swingx_es
misbehave.

>
> What I see too is that swingx_es.properties in swingx
> is the old version, before native2ascii.

yeah, I didn't yet commit your version because of the problem :-)

>
> How can I see search_es.png ?.

ahh... looks like attachment didn't make it to the forum (only to the
mailing list, what a nuisance...). All escaped chars are shown as
squares, that's the typical sign for something wrong with the encoding
(as Ricardo has seen - looks like listening to the mailing list :-).

Okay, wait a minute - I'll check what's in the incubator and then come
back here

Thanks
Jeanette

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

dags
Offline
Joined: 2003-06-10

Jeanette:

I checked swingx_de.properties (in swingx project) and seems that has not been processed with native2ascii. That confuses me! :-). Properties files must be processed with native2ascii or not ?.

Regards,
Diego.

kleopatra
Offline
Joined: 2003-06-11

> Jeanette:
>
> I checked swingx_de.properties (in swingx project)
> and seems that has not been processed with
> native2ascii. That confuses me! :-). Properties files
> must be processed with native2ascii or not ?.

got me - Yes, you are right and I'm lazy

here's a c&p of the start of the swingx_es (don't know what will happen in all the c&p):

# spanish properties for swingx
# JXSearchPanel
# @author: Diego Gil (dags in jdesktop)

Search.matchCase=Coincidencia de may\ufffdsculas/min\ufffdsculas
Search.contains=contiene
Search.equals=igual
Search.endsWith=termina con
Search.startsWith=empieza con

Search.wrapSearch=B\ufffdsqueda Circular
Search.backwardsSearch=Hacia Atr\ufffds

you see that all the escapes are the same? Maybe simply try again (native2ascii and commit?) - could be a weird error somewherer along the line.

Thanks
Jeanette

dags
Offline
Joined: 2003-06-10

Jeanette:

I saw it. I don't know what may be happened.

Fixed version (I hope) was committed to jdnc-incubator.

Please try it and let me know.

BTW, which mailing list should I suscribe to see attachments ?.

Regards,
Diego.

kleopatra
Offline
Joined: 2003-06-11

> Jeanette:
>
> I saw it. I don't know what may be happened.
>
> Fixed version (I hope) was committed to
> jdnc-incubator.
>

looks good now - thanks! I'll commit it soon to swingx.

>
> BTW, which mailing list should I suscribe to see
> attachments ?.

hmm, need to check myself (anybody else knows from the top of her head?) I would expect that swinglabs (main project) and then the mailing lists item on the nav-bar would lead to the shared list ... but maybe it#s better to wait a couple of days - a milestone release is pending (this or next friday :-) at which all mailing lists (at least those from the core subprojects as well) will be redirected to the common one - which might be renamed in the process. Really messy ... but the end of chaos is nearing

Jeanette

dags
Offline
Joined: 2003-06-10

Jeanette:

I am looking at swingx_es.properties in jdnc-incubator and can't find anything wrong. I used native2ascii as directed.

What I see too is that swingx_es.properties in swingx is the old version, before native2ascii.

How can I see search_es.png ?.

Diego.

Ricardo Lopes

a PNG is a image file format like JPG or GIF

The problem your are facing is for sure caused by encoding problems.

Ricardo Lopes.

jdnc-interest@javadesktop.org wrote:

>Jeanette:
>
>I am looking at swingx_es.properties in jdnc-incubator and can't find anything wrong. I used native2ascii as directed.
>
>What I see too is that swingx_es.properties in swingx is the old version, before native2ascii.
>
>How can I see search_es.png ?.
>
>Diego.
>---
>[Message sent by forum member 'dags' (Diego Gil)]
>
>http://www.javadesktop.org/forums/thread.jspa?messageID=119229
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
>For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
>
>
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

dags
Offline
Joined: 2003-06-10

I know what a png file is. I meant : where is search_es.png ?. It is supposed to be attached but I can't find it.

Regards,
Diego.