[Bug localedata/19982] New: Spelling mistake in french message for error code EXDEV.

["thomas.mijieux at ipb dot fr" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19982

            Bug ID: 19982
           Summary: Spelling mistake in french message for error code
                    EXDEV.
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: minor
          Priority: P2
         Component: localedata
          Assignee: unassigned at sourceware dot org
          Reporter: thomas.mijieux at ipb dot fr
                CC: libc-locales at sourceware dot org
  Target Milestone: ---

I found out that the french translation for "Invalid cross-device link"

was "Lien croisà de pÃriphÃque invalide" but this should be "pÃriphÃrique"
instead of "pÃriphÃque". (The two letters 'ri' have been omitted"

This is the message for the EXDEV error code which happen when you try to make
a hard link between two separated filesystems, or when you try to rename a file
between two filesystems.

if you happen to have /tmp and your home directory on different filesystems
(which is very likely), you may reproduce the problem like that:

in your home directory:
$ LANG=fr_FR.UTF-8 ln $(mktemp) .
> ln: impossible de crÃer le lien direct './tmp.UjrCWrqDBV' â '/tmp/tmp.UjrCWrqDBV': Lien croisà de pÃriphÃque invalide

The spelling mistake is present in the last version in glibc-2.23/po/fr.po .
______________________________________

Another issue is (but this may be more debatable) that this translation is not
very meaningful:
In the "Lien croisà de pÃriphÃrique invalide" sentence, "croisÃ" (which is the
translation of "cross") relates to "lien" (which stands for "link"). 

To me, this translation sounds more like if it was the translation of something
like "Invalid cross-link of device". Anyway in french, this does not relates
well to the problem and I think anybody would have to do serious investigation
to understand where the problem came from.

I think something like:
"Lien physique inter-pÃriphÃrique invalide" 
is a little better.

"Lien physique" stands for "Hard link": Even if there is no reference to hard
link in the english version, I think this is a good idea to precise that we are
speaking about hard links because this error only happens with hard links. A
symbolic link can cross filesystem boundaries, since it resolves to a path but
not to an inode.

-- 
You are receiving this mail because:
You are on the CC list for the bug.