[Geoserver-devel] Issues with new EntitéGénérique data folders

GeoServer GeoServer Developer
1

Hello All,

In the past week or so, I’ve been running into some issues with some of the new files added under /data, namely the two versions of “data/citensg-1.0/workspaces/sf/sf/EntitéGénérique”

As far as I can determine, there are two folders named the same thing, differing only in the unicode encoding of the “é”.

Some filesystems, including the macOS filesystem, don’t like this (similar to case-sensitive files).

Locally, these two folders are treated as the same folder, which means the files in them are permanently marked as modified and staged, since their contents differ between the two folders.

This makes using the geoserver repo rather difficult.

I have been able to workaround the issue by marking the files as locally ignored, which works fine as long as I stay on master, but means that I can’t switch to older branches that don’t have these files (I get a warning that the changes will get overwritten). This makes backporting commits quite difficult.
So far, I have not been able to find a workaround for changing branches - to do so I have to undo my local ignores, temporarily commit the problematic files, then checkout the old branch and do whatever I need to do there, then later reset the temporary commit when I return to the master branch.

So, I have a couple questions:

  1. Is anyone else having similar issues (I assume it is affecting all macOS developers, I wonder if it also affects Windows developers). If so, have you figured out any alternate workarounds?

  2. Is it absolutely necessary to have two folders with effectively the same name in the same directory? At the very least, is it possible to have them in different directories?

Torben

2

I know this issue well… I think I am actually be the cause of it :slight_smile: And yes, I have this issue consisently on osx and windows, linux seems to handle it a bit more gracefully.

I think your (2) question hints at the best solution going forward (at least that was the consensus the last time we discussed it iirc), and that is not to use the name of the directory as the absolute source of the feature type name, instead use what you find in the featuretype.xml config file. This would allow us to encode the directory names in a more universally file system friendly way, but still support feature types with “extended characters” in them.

Perhaps that is easier now with the recent work done to abstract away raw resource access, not sure.

$0.02

On November 28, 2017 at 11:15:24 AM, Torben Barsballe (tbarsballe@anonymised.com) wrote:

Hello All,

In the past week or so, I’ve been running into some issues with some of the new files added under /data, namely the two versions of “data/citensg-1.0/workspaces/sf/sf/EntitéGénérique”

As far as I can determine, there are two folders named the same thing, differing only in the unicode encoding of the “é”.

Some filesystems, including the macOS filesystem, don’t like this (similar to case-sensitive files).

Locally, these two folders are treated as the same folder, which means the files in them are permanently marked as modified and staged, since their contents differ between the two folders.

This makes using the geoserver repo rather difficult.

I have been able to workaround the issue by marking the files as locally ignored, which works fine as long as I stay on master, but means that I can’t switch to older branches that don’t have these files (I get a warning that the changes will get overwritten). This makes backporting commits quite difficult.
So far, I have not been able to find a workaround for changing branches - to do so I have to undo my local ignores, temporarily commit the problematic files, then checkout the old branch and do whatever I need to do there, then later reset the temporary commit when I return to the master branch.

So, I have a couple questions:

  1. Is anyone else having similar issues (I assume it is affecting all macOS developers, I wonder if it also affects Windows developers). If so, have you figured out any alternate workarounds?

  2. Is it absolutely necessary to have two folders with effectively the same name in the same directory? At the very least, is it possible to have them in different directories?

Torben

Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

3

Hi Torben,
I think that happend by accident… the NSG data directory has been copied from the WFS 1.1 one
and then edited via the UI.
My guess is that this editing created the directories with the accents, leaving the ones without there.

I’m at end of day here and still have to write a couple of tests for WFS 2.0 compat fixes, I’ll try to have
a look at it tomorrow

Cheers
Andrea

···

On Tue, Nov 28, 2017 at 7:14 PM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hello All,

In the past week or so, I’ve been running into some issues with some of the new files added under /data, namely the two versions of “data/citensg-1.0/workspaces/sf/sf/EntitéGénérique”

As far as I can determine, there are two folders named the same thing, differing only in the unicode encoding of the “é”.

Some filesystems, including the macOS filesystem, don’t like this (similar to case-sensitive files).

Locally, these two folders are treated as the same folder, which means the files in them are permanently marked as modified and staged, since their contents differ between the two folders.

This makes using the geoserver repo rather difficult.

I have been able to workaround the issue by marking the files as locally ignored, which works fine as long as I stay on master, but means that I can’t switch to older branches that don’t have these files (I get a warning that the changes will get overwritten). This makes backporting commits quite difficult.
So far, I have not been able to find a workaround for changing branches - to do so I have to undo my local ignores, temporarily commit the problematic files, then checkout the old branch and do whatever I need to do there, then later reset the temporary commit when I return to the master branch.

So, I have a couple questions:

  1. Is anyone else having similar issues (I assume it is affecting all macOS developers, I wonder if it also affects Windows developers). If so, have you figured out any alternate workarounds?

  2. Is it absolutely necessary to have two folders with effectively the same name in the same directory? At the very least, is it possible to have them in different directories?

Torben

Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

4

Hi Torben,
I made a tentative fix but there is nobody around herewith a Mac around to verify if it helps.
Let me know :slight_smile:

Cheers
Andrea

···

On Tue, Nov 28, 2017 at 7:31 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi Torben,
I think that happend by accident… the NSG data directory has been copied from the WFS 1.1 one
and then edited via the UI.
My guess is that this editing created the directories with the accents, leaving the ones without there.

I’m at end of day here and still have to write a couple of tests for WFS 2.0 compat fixes, I’ll try to have
a look at it tomorrow

Cheers
Andrea

–

On Tue, Nov 28, 2017 at 7:14 PM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hello All,

In the past week or so, I’ve been running into some issues with some of the new files added under /data, namely the two versions of “data/citensg-1.0/workspaces/sf/sf/EntitéGénérique”

As far as I can determine, there are two folders named the same thing, differing only in the unicode encoding of the “é”.

Some filesystems, including the macOS filesystem, don’t like this (similar to case-sensitive files).

Locally, these two folders are treated as the same folder, which means the files in them are permanently marked as modified and staged, since their contents differ between the two folders.

This makes using the geoserver repo rather difficult.

I have been able to workaround the issue by marking the files as locally ignored, which works fine as long as I stay on master, but means that I can’t switch to older branches that don’t have these files (I get a warning that the changes will get overwritten). This makes backporting commits quite difficult.
So far, I have not been able to find a workaround for changing branches - to do so I have to undo my local ignores, temporarily commit the problematic files, then checkout the old branch and do whatever I need to do there, then later reset the temporary commit when I return to the master branch.

So, I have a couple questions:

  1. Is anyone else having similar issues (I assume it is affecting all macOS developers, I wonder if it also affects Windows developers). If so, have you figured out any alternate workarounds?

  2. Is it absolutely necessary to have two folders with effectively the same name in the same directory? At the very least, is it possible to have them in different directories?

Torben

Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Geoserver-devel mailing list
Geoserver-devel@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

5

Hi Andrea

I updated to latest master, and everything is working fine for me now.

Thanks,

Torben

···

On Wed, Nov 29, 2017 at 9:26 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi Torben,
I made a tentative fix but there is nobody around herewith a Mac around to verify if it helps.
Let me know :slight_smile:

Cheers

Andrea

On Tue, Nov 28, 2017 at 7:31 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi Torben,
I think that happend by accident… the NSG data directory has been copied from the WFS 1.1 one
and then edited via the UI.
My guess is that this editing created the directories with the accents, leaving the ones without there.

I’m at end of day here and still have to write a couple of tests for WFS 2.0 compat fixes, I’ll try to have
a look at it tomorrow

Cheers
Andrea

–

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

On Tue, Nov 28, 2017 at 7:14 PM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hello All,

In the past week or so, I’ve been running into some issues with some of the new files added under /data, namely the two versions of “data/citensg-1.0/workspaces/sf/sf/EntitéGénérique”

As far as I can determine, there are two folders named the same thing, differing only in the unicode encoding of the “é”.

Some filesystems, including the macOS filesystem, don’t like this (similar to case-sensitive files).

Locally, these two folders are treated as the same folder, which means the files in them are permanently marked as modified and staged, since their contents differ between the two folders.

This makes using the geoserver repo rather difficult.

I have been able to workaround the issue by marking the files as locally ignored, which works fine as long as I stay on master, but means that I can’t switch to older branches that don’t have these files (I get a warning that the changes will get overwritten). This makes backporting commits quite difficult.
So far, I have not been able to find a workaround for changing branches - to do so I have to undo my local ignores, temporarily commit the problematic files, then checkout the old branch and do whatever I need to do there, then later reset the temporary commit when I return to the master branch.

So, I have a couple questions:

  1. Is anyone else having similar issues (I assume it is affecting all macOS developers, I wonder if it also affects Windows developers). If so, have you figured out any alternate workarounds?

  2. Is it absolutely necessary to have two folders with effectively the same name in the same directory? At the very least, is it possible to have them in different directories?

Torben

Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Geoserver-devel mailing list
Geoserver-devel@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

6

I just took a fresh checkout and have run into this problem, reading here explains the config “core.precomposeunicode” used (only on macOS) to address this.

Experimenting with defining the following before checkout:

git config --global -add core.precomposeunicode=true

···

–
Jody Garnett

On Wed, Nov 29, 2017 at 9:26 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi Torben,
I made a tentative fix but there is nobody around herewith a Mac around to verify if it helps.
Let me know :slight_smile:

Cheers

Andrea

On Tue, Nov 28, 2017 at 7:31 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi Torben,
I think that happend by accident… the NSG data directory has been copied from the WFS 1.1 one
and then edited via the UI.
My guess is that this editing created the directories with the accents, leaving the ones without there.

I’m at end of day here and still have to write a couple of tests for WFS 2.0 compat fixes, I’ll try to have
a look at it tomorrow

Cheers
Andrea

–

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

On Tue, Nov 28, 2017 at 7:14 PM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hello All,

In the past week or so, I’ve been running into some issues with some of the new files added under /data, namely the two versions of “data/citensg-1.0/workspaces/sf/sf/EntitéGénérique”

As far as I can determine, there are two folders named the same thing, differing only in the unicode encoding of the “é”.

Some filesystems, including the macOS filesystem, don’t like this (similar to case-sensitive files).

Locally, these two folders are treated as the same folder, which means the files in them are permanently marked as modified and staged, since their contents differ between the two folders.

This makes using the geoserver repo rather difficult.

I have been able to workaround the issue by marking the files as locally ignored, which works fine as long as I stay on master, but means that I can’t switch to older branches that don’t have these files (I get a warning that the changes will get overwritten). This makes backporting commits quite difficult.
So far, I have not been able to find a workaround for changing branches - to do so I have to undo my local ignores, temporarily commit the problematic files, then checkout the old branch and do whatever I need to do there, then later reset the temporary commit when I return to the master branch.

So, I have a couple questions:

  1. Is anyone else having similar issues (I assume it is affecting all macOS developers, I wonder if it also affects Windows developers). If so, have you figured out any alternate workarounds?

  2. Is it absolutely necessary to have two folders with effectively the same name in the same directory? At the very least, is it possible to have them in different directories?

Torben

Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.