Difference between revisions of "User:SilentFlame/Progress"

From Apertium
Jump to navigation Jump to search
Line 35: Line 35:
(Some of these are from coding challenges)
(Some of these are from coding challenges)


===deformatting===
===deformatting prototypes===
# Make the HTML format handler <code>apertium-deshtml</code> turn "&lt;i&gt;foo &lt;b&gt;bar&lt;/b&gt;&lt;/i&gt;" into "<nowiki>[{&lt;i&gt;}]foo [{&lt;i&gt;&lt;b&gt;}]bar</nowiki>"
# Make the HTML format handler <code>apertium-deshtml</code> turn "&lt;i&gt;foo &lt;b&gt;bar&lt;/b&gt;&lt;/i&gt;" into "<nowiki>[{&lt;i&gt;}]foo [{&lt;i&gt;&lt;b&gt;}]bar</nowiki>"
#* Code at https://github.com/SilentFlame/apertium/blob/master/challenge-1.cpp
#* Code at https://github.com/SilentFlame/apertium/blob/master/challenge-1.cpp
#* make <code>apertium-deshtml</code> *not* wrap tags like {{tag|p}} or {{tag|div}} in <code>{}</code> (ie. only for inline tags)
#* make <code>apertium-deshtml</code> *not* wrap tags like {{tag|p}} or {{tag|div}} in <code>{}</code> (ie. only for inline tags)
#* Code at https://github.com/SilentFlame/apertium/blob/master/challenge-2.cpp
#* Code at https://github.com/SilentFlame/apertium/blob/master/challenge-2.cpp



===pretransfer===
===pretransfer===

Revision as of 12:03, 14 May 2017

Progress on Automatic_blank_handling

Current task

Interchunk

  1. Apply changes to transfer.cc to interchunk.cc

TODO

Deformatters

Reformatters

lttoolbox

  • Make lt-proc correctly disperse inline blanks onto each lexical unit until the next [

postchunk

(Should be done after interchunk is complete)

etc

  • Ensure all other modules are fine with the new format for inline blanks
  • Work on other deformatters (mediawiki? latex?)

Done

(Some of these are from coding challenges)

deformatting prototypes

  1. Make the HTML format handler apertium-deshtml turn "<i>foo <b>bar</b></i>" into "[{<i>}]foo [{<i><b>}]bar"

pretransfer

transfer

  1. Fix a memory bug
    • uncommenting apertium/transfer.cc:1259 // delete[] format; in the blank handling branch leads to a double-free – find out why and ensure we're correctly releasing memory
    • Install valgrind from your package manager or http://valgrind.org/, then compile your program with -O0 -g3, then run valgrind -v --leak-check=full apertium/apertium-transfer and read the output