Difference between revisions of "User:SilentFlame/Progress"

From Apertium
Jump to navigation Jump to search
Line 53: Line 53:
 
# Fix a memory bug
 
# Fix a memory bug
 
#* uncommenting apertium/transfer.cc:1259 <code> // delete[] format;</code> in the blank handling branch leads to a double-free – find out why and ensure we're correctly releasing memory
 
#* uncommenting apertium/transfer.cc:1259 <code> // delete[] format;</code> 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 <code>valgrind -v --leak-check=full apertium/apertium-transfer</code> and read the output
+
#* Install valgrind from your package manager or http://valgrind.org/, then compile your program with -O0 -g3, then run <code>valgrind -v --leak-check=full apertium/apertium-transfer</code> and read the output

Revision as of 12:01, 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

  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