On Monday, 23/01/2017 10:32 GMT, Jeremie Courreges-Anglas wrote: > Davide Gerhard <rain...@irh.it> writes: > >> hello, >> just some fixes. > > Those don't look like "just fixes". There may be actual bug fixes here, > but other changes look intrusive. What about trying to prod/help > upstream so that those changes don't rot in our tree?
you are right, sorry; I did a mashup copying debian's patch set. bug fixes: - close every file after processing, not at the end of program. - recognize all <meta> tags, not just one. - correctly specify NULLs for 64-bit architectures. - substituted 'char*' with 'const char*' in needed places to avoid 'deprecated conversion from string constant to ‘char*’' warnings. - validate --width parameter input. - fix CXX variable on configure and now should compile with clang. changes/new features: - remove limited built-in http support. - support UTF-8 encoding when processing input. - don't use backspaces. - skip numbers in html tag. - recode input according to 'meta http-equiv' in html document. (needs iconv) - convert output to user's locale charset (needs iconv) I wrote to the developer but no answer yet. The utf-8 patch is done by him but he didn't released a new version with that therefore I am not so confident on a new release. The last one go back to 2004/2005. So, probably, we need to maintain some/all of those in ports. >> two questions: >> - how can I test the port with clang/llvm? some nice mk.conf variable? > > You can modify the port to add lang/llvm to MODULES, then tweak > MODCLANG_ARCHS and MODCLANG_LANGS. There is no user-level knob here, > ports are geared toward bulk builds. quite cumbersome in respect to CCX variable but it is good to know also this way. thanks jeremie. > >> - would be nice to add -utf8 to man: I need to use mg/vi or there >> is another tool? > > If you want to edit a manpage then yes, a text editor might help. :) I hoped in a wysiwyg software :)
