+# type: =head3
+#: ../src/guestfs.pod:619
+msgid "SYMLINKS ON NTFS-3G FILESYSTEMS"
+msgstr ""
+
+# type: textblock
+#: ../src/guestfs.pod:621
+msgid ""
+"Ntfs-3g tries to rewrite \"Junction Points\" and NTFS \"symbolic links\" to "
+"provide something which looks like a Linux symlink. The way it tries to do "
+"the rewriting is described here:"
+msgstr ""
+
+# type: textblock
+#: ../src/guestfs.pod:625
+msgid "L<http://www.tuxera.com/community/ntfs-3g-advanced/junction-points-and-symbolic-links/>"
+msgstr ""
+
+# type: textblock
+#: ../src/guestfs.pod:627
+msgid ""
+"The essential problem is that ntfs-3g simply does not have enough "
+"information to do a correct job. NTFS links can contain drive letters and "
+"references to external device GUIDs that ntfs-3g has no way of resolving. "
+"It is almost certainly the case that libguestfs callers should ignore what "
+"ntfs-3g does (ie. don't use L</guestfs_readlink> on NTFS volumes)."
+msgstr ""
+
+# type: textblock
+#: ../src/guestfs.pod:634
+msgid ""
+"Instead if you encounter a symbolic link on an ntfs-3g filesystem, use "
+"L</guestfs_lgetxattr> to read the C<system.ntfs_reparse_data> extended "
+"attribute, and read the raw reparse data from that (you can find the format "
+"documented in various places around the web)."
+msgstr ""
+
+# type: =head3
+#: ../src/guestfs.pod:639
+msgid "EXTENDED ATTRIBUTES ON NTFS-3G FILESYSTEMS"
+msgstr ""
+
+# type: textblock
+#: ../src/guestfs.pod:641
+msgid ""
+"There are other useful extended attributes that can be read from ntfs-3g "
+"filesystems (using L</guestfs_getxattr>). See:"
+msgstr ""
+
+# type: textblock
+#: ../src/guestfs.pod:644
+msgid "L<http://www.tuxera.com/community/ntfs-3g-advanced/extended-attributes/>"
+msgstr ""
+