Tag Info

New answers tagged


This still comes up on google searches so I wanted to put this on the record: pandoc could not read docx when this question was asked (the error comes from trying to read a binary file) but since version 1.13 it can, and it does a pretty good job of it.


maybe to visually inspect all ~1000 possibilities of iconv, by listing 20 first lines of each one ... merged to all.txt result. #!/usr/bin/env bash line=$(printf "=%.0s" {1..50}) for FMT in $(iconv -l); do echo "$line\nFormat $FMT:\n$line" iconv -f $FMT -t UTF8 < inputFile.srt | head -n20 done > all.txt ...


You could look at the source code of SubRip to determine the existing file format: http://sourceforge.net/projects/subrip/


The format of the file is probably little-endian UTF-16. Some apps on Windows seem to default to this, and it causes a lot of porability problems. vi represents ASCII-Nul (numerically zero) valued bytes as '^@' (control-At). You can actually enter zero-valued bytes in vim with the control-shift-@ chord. grep must see the ACII-Nul bytes, rather than ...


Yes, grep sw the ^@ characters. cat is printing the characters to the terminal, but they are characters you can't see. Just because you can't see the characters doesn't mean they aren't there. Your choice/preference, depending on which one works best for what you need. Remember, though, that vi has the possibility to change the file. ^@ is not a natural ...

Top 50 recent answers are included