-
Notifications
You must be signed in to change notification settings - Fork 39
Things for Next Release
With v0.31 out now, I expect tomboy-ng release cycles to be a little longer. Given that basic functionality is almost all there now, we can afford the luxury of a beta release cycle before formal release, the extra testing period will ensue a quality release and avoid bugs that sometimes creep in that require an unexpected (to me) combination to demonstrate.
Any, all or even none of these may make it into v0.32.
- Search and Replace.
- Pre load local search when landing in a note after doing a main search. At present we jump to the first found search term but if user actually wants a further one, they must initiate a full local search.
- Search backwards is unreliable.
Better to use the CommonMark markdown exporter I wrote for the NextCloud experiments, nice to be able to export a Notebook full of notes too.
I am still unconvienced that their API is suitable. So, this one is likely to be on hold.
A bit blue sky, but looks possible and maybe useful. If we can sync, in one-to-one mode, to a directory it may open up workflows facilatated by, eg, syncthing. The existing Android sync unit is a pretty good template, a new, and quite simple trans unit required.
Test to see if the MTP mounted filesystem from Tomdroid can be made work if the number of notes is kept quite small.
Progress Report : I now have a reasonable looking Tomdroid Sync, can do a one to one sync over a USB cable (needs no ssh, passwords and no profiles needed). Seems quite fast too. If you would like a alpha release to play with, please let me know.
A 'merge with any directory' is also possible with the same code, I would just need to provide some buttons....
Useful if we could associate (each separate) sync with a Notebook. That way, a user can declare a sync only involves certain notes. Need to model this a bit to ensure its safe.
It would be nice to be able to manage the Help Notes via the .po system. This would make maintaining them a lot simpler for translators. But there are some issues.
- Add an export in .po format.
- Add an import from .po format.
- Add an export to man page, html.....
- But must have some means of merging existing translated content with new content, ie what happens to *.es.po when *.po is overwritten ? That is starting to sound like an implementation of POEdit. Can we find a way to use POEdit to do that syncing ?
It appears msgmerge, part of gettext, might do it all. So, I propose a workflow to make / manage help notes like this -
- I add a dumb .po import/export capability.
- create a (disposable) tomboy note, either from scratch or by importing the appropriate (English) .po file.
- edit as required.
- Export that content from tomboy-ng to a .po or .pot file containing a limited sub set of common mark. This file becomes part of git distro.
- Use msgmerge to generate new *.XX.po files for each supported language. Normally, little will have changed, most of existing translations will be valid. New content will be, of course, by default in English.
- Translators will, at some stage, pull down their .po file, edit some or all and return it.
- At package time, I 'import' (cli desirable) each *.XX.po file generating a regular Tomboy format help note to distribute in the package.
- Man pages, pdf, html can be generated in the same way, to broaden appeal. Maybe ??
Progress Report : I have added (to TomboyTools) the ability to export a note in a sort of .pot file. It still has the xml markup in there so is quite hard to read IMHO. aguador is looking at some other tools that might be more suited to flowing, marked up text than poedit.