Workflow: Changes and additions
===============================

Things are continuously  developing or at least  changing. For example,
my  gVim on  my GPD  Pocket (Ubuntu  MATE 18.04)  has issues  with text
encoding.  If  I  create a  new  file  then  I  everything is  OK.  But
when  I  save  it  and  re-open it  then  it  en-codes  local  language
characters incorrectly.  It is  strange because I  have been  using the
same  .vimrc/.gvimrc for  ages on  several Linux  machines and  I never
encountered such behaviour.

The GPD is my main note-taking machine  for meetings so it is the major
issue here. I  have to use Pluma  (a MATE's GEdit fork)  which does not
have such  problems. But  I cannot  use is as  an outliner  (unlike the
Vim).

On my  Fedora system, the POWER9  Blackbird machine, it works.  But the
new TeXLive does  not accept my old LaTeX files  because of encoding. I
have had to add one line to every main file. It works now but I have to
verify if such files still compile on my SGI O2 and on the GPD.

In my pocket,  there are minimal changes. I have  found the Progect [1]
outliner. Its  free and nice  and it works on  Palm OS 3.x-5.x.  It can
export items to  the ToDo application and export formatted  text to the
MemoPad (as a way to get them  out of the Palm easily). I installed the
Progect on all my Palms which are have at the moment (a IIIx, a TRGpro,
a T|W and the Aeeca PDA32). It works everywhere and it can be (sort of)
synchronised also by beaming of a data file.

I have  thought that I  will be  able to replace  my aging (and  - more
importantly - heavily  used) Palm IIIxe with the Tungsten  W because of
its  excellent, sunlight-readable  screen  and its  tiny but  excellent
keyboard, I  have found that T|W's  battery life is still  excellent (a
week or my  normal use on its original, fifteen  years old, battery). I
even got  three spare  styli (it  was an  original Palm-branded  set of
three with  replaceable tops to fit  both T|W/T|C machines and  the T|X
ones) and the latest model of the KODAK PalmPix camera.

But I have  found one issue which probably has  no solution: I actually
CAN easily  synchronise the  Palm IIIxe with  my latest  desktop (which
runs the Fedora 31 on POWER9). The only necessary thing is a USB-serial
adapter (which I have). But  I CANNOT reliably synchronise the Tungsten
W. And  I have to  synchronize data  and circulate files  frequently so
this is a problem.

The Aceeca  works better  here -  it synchronises  via USB,  The serial
connection on the III is still better  (it just works - fot the Aeeca's
OS  5.x I  have to  do "modprobe  visor" first,  the press  the HotSync
button  or icon  on an  Aceeca  and only  after  then I  can issue  the
synchronisation command  on the desktop...).  But in this case  the USB
works at least quickly and reliably.  The problem is that the Aceeca is
bulky and it  does not have some useful features:  there is no infrared
(so  no beaming  to other  devices), it  has no  sound hardware  (so no
music) and its system is relatively fragile: it likes to hand or reboot
after installation on  many applications (which work  without issues on
Palm OS  3.x and/or  4.x). Also  if the keyboard  driver is  active but
Bluetooth is off the device can hang on an "Allow Bluetooth" dialog.

So I have replaced  my IIIxe with a TRGpro (itself  a IIIx/IIIxe with a
CF card slot, and with louder alarm)...


References:

[1] http://progect.sf.net