[GeoNetwork-users] missing strings at main page

Hi list,

I wanted to load geonetwork with srv/de/main.home and changed index.html and
config.xml which worked (geonetwork version 2.6 unstable). But after restart of
tomcat 6 all my strings at main page of geonetwork are gone like there isn`t a
connection to strings.xml.

Could that be I`ve changed other .js files like gn.search.js and gn_search.js?
Or where are my mistake?

Any tipps or suggestions?

thanks
best regards
Sarah

Hi Sarah_S!

That´s got nothing to do with a missing connection to anything. The reason
is simple:

Many of the files from Geonetwork 2.6.0 are typed in the wrong encoding. For
example, many are typed in ANSI, but the file says it is UTF-8. This does
not matter for English, but most of the other languages which use special
characters like ß, ö, ü etc.

First make sure, a file consists only of characters in the correct encoding.
One letter typed in wrong encoding and you won´t see any of the words from
the main-page GUI. You may change the encoding even with the small editor
from XP, for example. You may use UltraEdit or something else.

After that validate the xml with e.g. validome.org and test it for "Nur auf
Wohlgeformtheit prüfen".

If the file stings.xml is written in the correct encoding and it is well
formed xml, you will have all of the strings at the main page back again.

Good luck!
Anja
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/missing-strings-at-main-page-tp5755450p5765817.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.

Hi Anja,
That's an important observation! Could you be more specific to which files you found with a wrong encoding? I sometimes check encoding of files and had the impression most are actually correctly encoded in UTF-8. If you could list them in a ticket on trac that would even be better, unless they are really many.
Thanks and regards,
Jeroen

On 23 nov 2010, at 09:25, Anja wrote:

Hi Sarah_S!

That´s got nothing to do with a missing connection to anything. The reason
is simple:

Many of the files from Geonetwork 2.6.0 are typed in the wrong encoding. For
example, many are typed in ANSI, but the file says it is UTF-8. This does
not matter for English, but most of the other languages which use special
characters like ß, ö, ü etc.

First make sure, a file consists only of characters in the correct encoding.
One letter typed in wrong encoding and you won´t see any of the words from
the main-page GUI. You may change the encoding even with the small editor
from XP, for example. You may use UltraEdit or something else.

After that validate the xml with e.g. validome.org and test it for "Nur auf
Wohlgeformtheit prüfen".

If the file stings.xml is written in the correct encoding and it is well
formed xml, you will have all of the strings at the main page back again.

Good luck!
Anja
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/missing-strings-at-main-page-tp5755450p5765817.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
Best Open Source Mac Front-Ends 2024
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

Thanks Anja for that information!

I will look at that point.

best regards
Sarah

________________________________

Hi Sarah_S!

That´s got nothing to do with a missing connection to anything. The reason
is simple:

Many of the files from Geonetwork 2.6.0 are typed in the wrong encoding. For
example, many are typed in ANSI, but the file says it is UTF-8. This does
not matter for English, but most of the other languages which use special
characters like ß, ö, ü etc.

First make sure, a file consists only of characters in the correct encoding.
One letter typed in wrong encoding and you won´t see any of the words from
the main-page GUI. You may change the encoding even with the small editor
from XP, for example. You may use UltraEdit or something else.

After that validate the xml with e.g. validome.org and test it for "Nur auf
Wohlgeformtheit prüfen".

If the file stings.xml is written in the correct encoding and it is well
formed xml, you will have all of the strings at the main page back again.

Good luck!
Anja
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/missing-strings-at-main-page-tp5755450p5765817.html

Sent from the GeoNetwork users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Hi Jeroen,

I overview-checked the files in /webapps/geonetwork/loc/

In /de and /en most of the files have ANSI-Encoding although they should
have UTF-8.

But it is a problem with "ordinary" files as well. I do not know whether it
is important, but maybe it was better all of the readable files should have
UTF-8 Encoding. Many of the others like

/webapps/geonetwork/WEB-INF/

have ANSI -Encoding as well: config_csw.xml, config_gui.xml...

The thing is, that some xml say they are ISO-8859-1 encoded and they truely
are (e.g. config-export.xml), but others in the same directory say they are
UTF-8 and are ANSI written. it is a mixture. It is not one specific file,
but to me it looks like a general problem. Perhaps it is a solution to have
all of the files written in UTF-8 and none of the files left to ISO-8859-1.
So it´d be clearly arranged.

Sorry I cannot help you any further. It must be dull work for somebody
checking over all of the files. I use Notpad++ for this, whenever I find
something that does not work. Notepad++ shows the written encoding in the
footer ("ANSI as UTF-8", "UTF-8", "ANSI" and so on) and you can easily
change from one encoding to another. I do not know any tool that is able to
look for "wrong" characters. Off course, that are those ones you cannot read
properly on your screen...

Greetings
Anja

Hi Anja,
That's an important observation! Could you be more specific to which files
you found with a wrong encoding? I sometimes check encoding of files and had
the impression most are actually correctly encoded in UTF-8. If you could
list them in a ticket on trac that would even be better, unless they are
really many.
Thanks and regards,
Jeroen

On 23 nov 2010, at 09:25, Anja wrote:

Hi Sarah_S!

That´s got nothing to do with a missing connection to anything. The reason
is simple:

Many of the files from Geonetwork 2.6.0 are typed in the wrong encoding.
For
example, many are typed in ANSI, but the file says it is UTF-8. This does
not matter for English, but most of the other languages which use special
characters like ß, ö, ü etc.

...
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/missing-strings-at-main-page-tp5755450p5766266.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.

Hi Anja,
We've been checking a large number of xml files and xsl files on different operating systems. We tested using BBEdit on OS X and Notepad++ on Windows.

We found that all these files have the correct UTF-8 encoding, or in some cases the encoding in line with what has been specified in the XML document.

If you could, it would be great if you can investigate more precisely what reasons there may be that you find other encodings?

Could you attach a file that you did not edit before so we can compare it to the original?

Kind regards,
Jeroen

On 23 nov 2010, at 12:26, Anja wrote:

Hi Jeroen,

I overview-checked the files in /webapps/geonetwork/loc/

In /de and /en most of the files have ANSI-Encoding although they should
have UTF-8.

But it is a problem with "ordinary" files as well. I do not know whether it
is important, but maybe it was better all of the readable files should have
UTF-8 Encoding. Many of the others like

/webapps/geonetwork/WEB-INF/

have ANSI -Encoding as well: config_csw.xml, config_gui.xml...

The thing is, that some xml say they are ISO-8859-1 encoded and they truely
are (e.g. config-export.xml), but others in the same directory say they are
UTF-8 and are ANSI written. it is a mixture. It is not one specific file,
but to me it looks like a general problem. Perhaps it is a solution to have
all of the files written in UTF-8 and none of the files left to ISO-8859-1.
So it´d be clearly arranged.

Sorry I cannot help you any further. It must be dull work for somebody
checking over all of the files. I use Notpad++ for this, whenever I find
something that does not work. Notepad++ shows the written encoding in the
footer ("ANSI as UTF-8", "UTF-8", "ANSI" and so on) and you can easily
change from one encoding to another. I do not know any tool that is able to
look for "wrong" characters. Off course, that are those ones you cannot read
properly on your screen...

Greetings
Anja

Hi Anja,
That's an important observation! Could you be more specific to which files
you found with a wrong encoding? I sometimes check encoding of files and had
the impression most are actually correctly encoded in UTF-8. If you could
list them in a ticket on trac that would even be better, unless they are
really many.
Thanks and regards,
Jeroen

On 23 nov 2010, at 09:25, Anja wrote:

Hi Sarah_S!

That´s got nothing to do with a missing connection to anything. The reason
is simple:

Many of the files from Geonetwork 2.6.0 are typed in the wrong encoding.
For
example, many are typed in ANSI, but the file says it is UTF-8. This does
not matter for English, but most of the other languages which use special
characters like ß, ö, ü etc.

...
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/missing-strings-at-main-page-tp5755450p5766266.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
Best Open Source Mac Front-Ends 2024
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

Hi Jeroen,

our system administrator promised me to provide me with more detailed
information on installing GeoNetwork by tomororrw. Until then please find
attached three zipped files from /webapps/geonetwork/loc/en/xml

about.xml >> ANSI
iso-languages.xml >> ANSI as UTF-8
strings.xml >> UTF-8

I think all of the other files in this directory are ANSI on our server.

Due to our system administrator we installed OpenSuse 11.2. He also had a go
with Debian Linux, but this is not allowed officially in our environment. There
haven´t been any problems on Debian Linux. It is just that OpenSuse 11.2 seems
not be able to handle UTF-8 in the needed way. And so the encodings of the files
change to whatever "is needed" at that very moment. If there are special
characters Suse seems to use UTF-8. If there are a few special characters
encoding changes to ANSI as UTF-8 and it a file does not contain any special
characters it becomes ANSI.

I hope to be able to provide you with more detailed information by tomorrow.

Greetings
Anja

Jeroen Ticheler <jeroen.ticheler@anonymised.com> hat am 23. November 2010 um 14:19
geschrieben:

Hi Anja,
We've been checking a large number of xml files and xsl files on different
operating systems. We tested using BBEdit on OS X and Notepad++ on Windows.

We found that all these files have the correct UTF-8 encoding, or in some
cases the encoding in line with what has been specified in the XML document.

If you could, it would be great if you can investigate more precisely what
reasons there may be that you find other encodings?

Could you attach a file that you did not edit before so we can compare it to
the original?

Kind regards,
Jeroen

On 23 nov 2010, at 12:26, Anja wrote:

>
> Hi Jeroen,
>
> I overview-checked the files in /webapps/geonetwork/loc/
>
> In /de and /en most of the files have ANSI-Encoding although they should
> have UTF-8.
>
> But it is a problem with "ordinary" files as well. I do not know whether it
> is important, but maybe it was better all of the readable files should have
> UTF-8 Encoding. Many of the others like
>
> /webapps/geonetwork/WEB-INF/
>
> have ANSI -Encoding as well: config_csw.xml, config_gui.xml...
>
> The thing is, that some xml say they are ISO-8859-1 encoded and they truely
> are (e.g. config-export.xml), but others in the same directory say they are
> UTF-8 and are ANSI written. it is a mixture. It is not one specific file,
> but to me it looks like a general problem. Perhaps it is a solution to have
> all of the files written in UTF-8 and none of the files left to ISO-8859-1.
> So it´d be clearly arranged.
>
> Sorry I cannot help you any further. It must be dull work for somebody
> checking over all of the files. I use Notpad++ for this, whenever I find
> something that does not work. Notepad++ shows the written encoding in the
> footer ("ANSI as UTF-8", "UTF-8", "ANSI" and so on) and you can easily
> change from one encoding to another. I do not know any tool that is able to
> look for "wrong" characters. Off course, that are those ones you cannot read
> properly on your screen...
>
> Greetings
> Anja
>
>
>
> Hi Anja,
> That's an important observation! Could you be more specific to which files
> you found with a wrong encoding? I sometimes check encoding of files and had
> the impression most are actually correctly encoded in UTF-8. If you could
> list them in a ticket on trac that would even be better, unless they are
> really many.
> Thanks and regards,
> Jeroen
>
> On 23 nov 2010, at 09:25, Anja wrote:
>
>>
>> Hi Sarah_S!
>>
>> That´s got nothing to do with a missing connection to anything. The reason
>> is simple:
>>
>> Many of the files from Geonetwork 2.6.0 are typed in the wrong encoding.
>> For
>> example, many are typed in ANSI, but the file says it is UTF-8. This does
>> not matter for English, but most of the other languages which use special
>> characters like ß, ö, ü etc.
>>
> ...
> --
> View this message in context:
> http://osgeo-org.1803224.n2.nabble.com/missing-strings-at-main-page-tp5755450p5766266.html
> Sent from the GeoNetwork users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork

(attachments)

encoding_samples.zip (19.4 KB)

Hi

I checked the files (in Mac). I put results reported by BBEdit:

about.xml => UTF-8
iso-languages.xml => UTF-8
strings.xml => UTF-8 with BOM

All of them with Windows CRLF.

In Notepad++, for about.xml and iso-languages.xml says ANSI as UTF-8
(corresponds to UTF-8 without BOM).

Not really sure what really means about BOM, but seem to be managed
correctly as UTF-8 (at least in some systems) need to be encoded as UTF-8
with BOM.

Regards,
Jose García

On Tue, Nov 23, 2010 at 3:00 PM, moonbeam@anonymised.com
<moonbeam@anonymised.com>wrote:

Hi Jeroen,

our system administrator promised me to provide me with more detailed
information on installing GeoNetwork by tomororrw. Until then please find
attached three zipped files from /webapps/geonetwork/loc/en/xml

about.xml >> ANSI
iso-languages.xml >> ANSI as UTF-8
strings.xml >> UTF-8

I think all of the other files in this directory are ANSI on our server.

Due to our system administrator we installed OpenSuse 11.2. He also had a
go
with Debian Linux, but this is not allowed officially in our environment.
There
haven´t been any problems on Debian Linux. It is just that OpenSuse 11.2
seems
not be able to handle UTF-8 in the needed way. And so the encodings of the
files
change to whatever "is needed" at that very moment. If there are special
characters Suse seems to use UTF-8. If there are a few special characters
encoding changes to ANSI as UTF-8 and it a file does not contain any
special
characters it becomes ANSI.

I hope to be able to provide you with more detailed information by
tomorrow.

Greetings
Anja

Jeroen Ticheler <jeroen.ticheler@anonymised.com> hat am 23. November 2010 um
14:19
geschrieben:

> Hi Anja,
> We've been checking a large number of xml files and xsl files on
different
> operating systems. We tested using BBEdit on OS X and Notepad++ on
Windows.
>
> We found that all these files have the correct UTF-8 encoding, or in some
> cases the encoding in line with what has been specified in the XML
document.
>
> If you could, it would be great if you can investigate more precisely
what
> reasons there may be that you find other encodings?
>
> Could you attach a file that you did not edit before so we can compare it
to
> the original?
>
> Kind regards,
> Jeroen
>
>
> On 23 nov 2010, at 12:26, Anja wrote:
>
> >
> > Hi Jeroen,
> >
> > I overview-checked the files in /webapps/geonetwork/loc/
> >
> > In /de and /en most of the files have ANSI-Encoding although they
should
> > have UTF-8.
> >
> > But it is a problem with "ordinary" files as well. I do not know
whether it
> > is important, but maybe it was better all of the readable files should
have
> > UTF-8 Encoding. Many of the others like
> >
> > /webapps/geonetwork/WEB-INF/
> >
> > have ANSI -Encoding as well: config_csw.xml, config_gui.xml...
> >
> > The thing is, that some xml say they are ISO-8859-1 encoded and they
truely
> > are (e.g. config-export.xml), but others in the same directory say they
are
> > UTF-8 and are ANSI written. it is a mixture. It is not one specific
file,
> > but to me it looks like a general problem. Perhaps it is a solution to
have
> > all of the files written in UTF-8 and none of the files left to
ISO-8859-1.
> > So it´d be clearly arranged.
> >
> > Sorry I cannot help you any further. It must be dull work for somebody
> > checking over all of the files. I use Notpad++ for this, whenever I
find
> > something that does not work. Notepad++ shows the written encoding in
the
> > footer ("ANSI as UTF-8", "UTF-8", "ANSI" and so on) and you can easily
> > change from one encoding to another. I do not know any tool that is
able to
> > look for "wrong" characters. Off course, that are those ones you cannot
read
> > properly on your screen...
> >
> > Greetings
> > Anja
> >
> >
> >
> > Hi Anja,
> > That's an important observation! Could you be more specific to which
files
> > you found with a wrong encoding? I sometimes check encoding of files
and had
> > the impression most are actually correctly encoded in UTF-8. If you
could
> > list them in a ticket on trac that would even be better, unless they
are
> > really many.
> > Thanks and regards,
> > Jeroen
> >
> > On 23 nov 2010, at 09:25, Anja wrote:
> >
> >>
> >> Hi Sarah_S!
> >>
> >> That´s got nothing to do with a missing connection to anything. The
reason
> >> is simple:
> >>
> >> Many of the files from Geonetwork 2.6.0 are typed in the wrong
encoding.
> >> For
> >> example, many are typed in ANSI, but the file says it is UTF-8. This
does
> >> not matter for English, but most of the other languages which use
special
> >> characters like ß, ö, ü etc.
> >>
> > ...
> > --
> > View this message in context:
> >
http://osgeo-org.1803224.n2.nabble.com/missing-strings-at-main-page-tp5755450p5766266.html
> > Sent from the GeoNetwork users mailing list archive at Nabble.com.
> >
> >
------------------------------------------------------------------------------
> > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> > Tap into the largest installed PC base & get more eyes on your game by
> > optimizing for Intel(R) Graphics Technology. Get started today with the
> > Intel(R) Software Partner Program. Five $500 cash prizes are up for
grabs.
> > http://p.sf.net/sfu/intelisp-dev2dev
> > _______________________________________________
> > GeoNetwork-users mailing list
> > GeoNetwork-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> > GeoNetwork OpenSource is maintained at
> > http://sourceforge.net/projects/geonetwork
>

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork