X-Git-Url: https://git.deb.at/?a=blobdiff_plain;f=FAQ;h=d4689ac1676cfab1353d550aeeeda5c1f7ac7d1d;hb=079c2d798d85c2711642d41862b67eb459a182ae;hp=095db535242830956de3fd302c7225cd690d6fe5;hpb=5b536f8ab04f16f8383ef01ddec36eae6d272b6f;p=pkg%2Fabook.git

diff --git a/FAQ b/FAQ
index 095db53..d4689ac 100644
--- a/FAQ
+++ b/FAQ
@@ -31,10 +31,39 @@ A: Yes, it is possible starting from abook 0.4.15. See --add-email
    command line option and README.
 
 
-Q: Does abook support palm addressbooks?
-
-A: No, but there are utilities to convert palm addressbooks to ldif
-   files. Abook can import ldif files.
+Q: How can I import my abook entries to my PalmOS addressbook?
+
+A: Export to palmcsv format, and import from there. Several GUI
+   applications such as jpilot can do this, but the simplest way is to
+   use pilot-addresses from the pilot-link package. Just export to
+   addresses.palmcsv, then run this:
+                                                                                
+   pilot-addresses -d abook -c abook -r addresses.palmcsv
+                                                                                
+   This will delete everything in the abook category and replace it with
+   the latest information from your abook database. By keeping your
+   abook entries in a separate category, you can continue to add and
+   modify entries in other categories manually, and pilot-addresses will
+   not change or delete them.
+   (This entry was contributed by Jeff Covey)
+
+Q: Can I use abook in UTF-8 terminal emulator?
+
+A: Yes, version 0.5.2 added multibyte character support.
+
+   There are currently some issues:
+
+   - Addressbook files must have the same encoding as you use with abook.
+     If you have used abook previously with ISO-8859-1 encoding you can
+     convert the addressbook files with iconv(1). For example:
+
+     $ iconv -f ISO-8859-1 -t UTF-8 < ~/.abook/addressbook.old > \
+     ~/.abook/addressbook.new
+
+   - Filters will output strings using multibyte representation of the used
+     locale. This is incorrect for (most of) filters. You can again use
+     iconv to convert between encodings. Same goes with input filters. If
+     you use UTF-8 charset the input is expected to be UTF-8 encoded.
 
 
 last update: $Date$