By jumping two columns when wide character prints,
and draw wide background under wide character.
---
clients/terminal.c | 31 +--
1 file changed, 29 insertions(+), 2 deletions(-)
diff --git a/clients/terminal.c b/clients/terminal.c
index 6701fb6..9da1a56 100644
--- a/
Hi,
I used ZERO WIDTH SPACE(U+200B) as the invalid UTF-8 character, also ignore
these filler cells in terminal_send_selection.
Please review it again, thanks.
Peng Wu (1):
Fixes CJK wide character display
clients/terminal.c | 31 +--
1 file changed, 29 insertio
There have been a lot of questions asked lately about versioning of
interfaces and protocol objects. This addition to the documentation should
clear up some of those questions.
Signed-off-by: Jason Ekstrand
---
doc/publican/sources/Protocol.xml | 61 +++
1 fi
On Sun, Aug 18, 2013 at 1:28 AM, Bardur Arantsson wrote:
> On 2013-08-18 00:31, Jason Ekstrand wrote:
> > There have been a lot of questions asked lately about versioning of
> > interfaces and protocol objects. This addition to the documentation
> should
> > clear up some of those questions.
> >
The method described of alocation IDs has been wrong at least since version
1.0. This commit updates it to correspond to the way IDs are chosen in
versions >= 1.0.
Signed-off-by: Jason Ekstrand
---
doc/publican/sources/Protocol.xml | 14 ++
1 file changed, 10 insertions(+), 4 deleti
On Sun, Aug 18, 2013 at 2:33 AM, Ilyes Gouta wrote:
>
> On Aug 17, 2013 11:32 PM, "Jason Ekstrand" wrote:
> >
> > The method described of alocation IDs has been wrong at least since
> version
> > 1.0. This commit updates it to correspond to the way IDs are chosen in
> > versions >= 1.0.
> >
> >
On Aug 17, 2013 11:32 PM, "Jason Ekstrand" wrote:
>
> The method described of alocation IDs has been wrong at least since
version
> 1.0. This commit updates it to correspond to the way IDs are chosen in
> versions >= 1.0.
>
> Signed-off-by: Jason Ekstrand
> ---
> doc/publican/sources/Protocol.x
On 2013-08-18 00:31, Jason Ekstrand wrote:
> There have been a lot of questions asked lately about versioning of
> interfaces and protocol objects. This addition to the documentation should
> clear up some of those questions.
>
> +
> + In order to keep things sane, this has a few implica
