> Date: Sun, 22 Jul 2012 17:01:30 +0200 > From: Jacob Nordfalk <[email protected]> > To: [email protected] > Reply-To: [email protected] > Subject: Re: [Apertium-stuff] New applications: Apertium Caffeine andApertium > plug-in for OmegaT > > (..................) > > ======= > > > WRT formatters and deformatters I think its fine to make a simple > (de)formatter like the one needed for omegaT or for HTML, if you anticipate > they are needed for plugins. More advanced (de)formatters is for the C++ > version, which has a sophisticated (some would say complicated :-) way of > (de)formatting which I *don't* recommend you to look into. > > But you could play with the C++ version to get a feel of it. For example: > > $ echo "I am <b>fine</> and all. :-)" | apertium-deshtml > > I am[ <b>]fine[<\/b> ]and all. :-).[][ > ] > > > $ echo "I am <b>fine</b> and all. :-)" | apertium-deshtml | > apertium-rehtml > I am <b>fine</b> and all. :-) > > Stephen Tigener worked with the text formatter. Probably, if he have time, > he could quickly put something together. > > > Jacob > > --
As to me, I think since several months to write formatters and deformatters for man pages and also for mnémonic interface files (on each line, an identifier not to be changed on the left side and a printf formatted string on the right side). I recently watched destxt source file to see the programming style but I felt surprised to see a so big source just to do what it is supposed to do. My source files would be really shorter. If it is not considered as a crime to use non UTF-8 texts for translations I would think also nice to add the suffix iso to the name of the format. So, the options -f txtiso , -f htmliso, -f maniso and -f mnemoiso (some more ?) would start converting to UTF-8 a ISO-8859-1 (or close ISO-8859-n variants) input file before formatting, translating, deformatting and putting again with ISO-8859-1 charset (assuming source and target languages both use west european alphabet). As these new features would mainly consist in adding new files, I don't know the best place to put them : - directly in apertium trunk when they work - in incubator with a full copy of the other apertium files found in trunk - in incubator but only new files and changed files (like the makefile), so it would be necessary to use the others apertium files of trunk to complile and install the whole. And I have the same question for developping the other translation direction of an allready released pair. -------------------------------- Bernard Chardonneau (France) Phone : [33] 1 64 90 87 04 (from Sept to June except holidays) GSM phone : [33] 6 49 95 13 95 (french scholl holidays, C zone) Multilingual websites for my free softwares : http://libremail.free.fr and http://libremail.tuxfamily.org http://cyloop.tuxfamily.org (mainly translated with Apertium) My general website (in french only) http://bech.free.fr ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
