Difference between revisions of "User:SilentFlame/Progress"

From Apertium
Jump to navigation Jump to search
Line 28: Line 28:
 
===transfer (non-chunking)===
 
===transfer (non-chunking)===
 
* Test if current transfer.cc handles non-chunking/single-stage transfer correctly, if not, fix
 
* Test if current transfer.cc handles non-chunking/single-stage transfer correctly, if not, fix
  +
* Task: PR to https://github.com/unhammer/apertium/ with tests showing working transfer.cc for single-stage/non-chunking transfer, with inline vs block-level blank handling
   
 
===postchunk===
 
===postchunk===

Revision as of 12:10, 14 May 2017

Progress on Automatic_blank_handling

Current task

Interchunk

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

TODO

Deformatters

Reformatters

lttoolbox

transfer (non-chunking)

  • Test if current transfer.cc handles non-chunking/single-stage transfer correctly, if not, fix
  • Task: PR to https://github.com/unhammer/apertium/ with tests showing working transfer.cc for single-stage/non-chunking transfer, with inline vs block-level blank handling

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 (chunker)

  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