X-Git-Url: https://git.deb.at/w?a=blobdiff_plain;f=FAQ;h=8295adedd28d9871130d2ffd02d3ed344f011204;hb=81aa461acc64a30237ba7fa3d30e361f9a074689;hp=e96731a848511ef9c6835bf18925cd71d0ea833b;hpb=7dca83329bb3ce545d6d03e10754999b9a82ca01;p=pkg%2Fabook.git diff --git a/FAQ b/FAQ index e96731a..8295ade 100644 --- a/FAQ +++ b/FAQ @@ -1,6 +1,11 @@ abook FAQ ~~~~~~~~~ +Q: Can I recall the old value in editor? + +A: Yes, use up arrow to recall the old value. + + Q: How to query all addresses when I press 'Q' in mutt? A: Type "all" to the prompt. @@ -26,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? +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 -A: No, but there are utilities to convert palm addressbooks to ldif - files. Abook can import ldif files. + - 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: 2001/10/17 16:31:04 $ +last update: $Date: 2004/02/18 19:48:46 $