You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As for now vimhelp provides its own option to wrap the text textwidth. I would suggest to use the generic TransTractor's one wrapcol instead (which is controlled by -w/--width option of the scripts).
As for now the generic default is 76, but the VimHelp's is 78. Is this correct?
As for now vimhelp provides its own option to wrap the text textwidth. I would suggest to use the generic TransTractor's one wrapcol instead (which is controlled by -w/--width option of the scripts).
Good catch! That option is indeed more suitable for this purpose. Since the VimHelp format support hasn't been released yet, removing the textwidth option seems reasonable.
As for now the generic default is 76, but the VimHelp's is 78. Is this correct?
Also there is codeblock splitting into several paragraphes. Is it actually desirable?
I prefer this approach since it results in smaller messages in the PO file. However, it might be beneficial to have an option to change this behavior if combined code block messages are preferred.
This is off-topic to the issue title, but I've noticed code blocks can also start with >vim (followed by a line end). Currently, only > is supported (ref. example).
As for now vimhelp provides its own option to wrap the text
textwidth
. I would suggest to use the generic TransTractor's onewrapcol
instead (which is controlled by-w
/--width
option of the scripts).As for now the generic default is
76
, but the VimHelp's is78
. Is this correct?@gemmaro, any objections?
The text was updated successfully, but these errors were encountered: