Incompatibility between babel-french and tasks

Clash Royale CLAN TAG#URR8PPP

up vote
1
down vote

favorite

There seems to be an incompatibility between these two packages.

Look at these two MWE:

The right one

documentclassarticle
usepackagetasks
%usepackage[french]babel
begindocument

begintasks(3)
task aaa
task! fff 
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

The wrong one

documentclassarticle
usepackagetasks
usepackage[french]babel
begindocument

begintasks(3)
task aaa
task! fff 
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

• This post is to report this incompatibility




• Does someone have an nice idea on how to solve this issue?

babel incompatibility bugs tasks

share|improve this question

asked 1 hour ago

Colas

1,04321454

add a comment | 

up vote
1
down vote

favorite

There seems to be an incompatibility between these two packages.

Look at these two MWE:

The right one

documentclassarticle
usepackagetasks
%usepackage[french]babel
begindocument

begintasks(3)
task aaa
task! fff 
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

The wrong one

documentclassarticle
usepackagetasks
usepackage[french]babel
begindocument

begintasks(3)
task aaa
task! fff 
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

• This post is to report this incompatibility




• Does someone have an nice idea on how to solve this issue?

babel incompatibility bugs tasks

share|improve this question

asked 1 hour ago

Colas

1,04321454

add a comment | 

up vote
1
down vote

favorite

up vote
1
down vote

favorite

There seems to be an incompatibility between these two packages.

Look at these two MWE:

The right one

documentclassarticle
usepackagetasks
%usepackage[french]babel
begindocument

begintasks(3)
task aaa
task! fff 
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

The wrong one

documentclassarticle
usepackagetasks
usepackage[french]babel
begindocument

begintasks(3)
task aaa
task! fff 
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

• This post is to report this incompatibility




• Does someone have an nice idea on how to solve this issue?

babel incompatibility bugs tasks

share|improve this question

asked 1 hour ago

Colas

1,04321454

There seems to be an incompatibility between these two packages.

Look at these two MWE:

The right one

documentclassarticle
usepackagetasks
%usepackage[french]babel
begindocument

begintasks(3)
task aaa
task! fff 
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

The wrong one

documentclassarticle
usepackagetasks
usepackage[french]babel
begindocument

begintasks(3)
task aaa
task! fff 
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

• This post is to report this incompatibility




• Does someone have an nice idea on how to solve this issue?

babel incompatibility bugs tasks

babel incompatibility bugs tasks

share|improve this question

asked 1 hour ago

Colas

1,04321454

share|improve this question

asked 1 hour ago

Colas

1,04321454

share|improve this question

share|improve this question

asked 1 hour ago

Colas

1,04321454

asked 1 hour ago

Colas

1,04321454

asked 1 hour ago

Colas

1,04321454

1,04321454

add a comment | 

add a comment | 

1 Answer
1

active

oldest

votes

up vote
3
down vote

I wouldn't call this "solving", but you can use etoolbox's AtBeginEnvironment hook to deactivate the ! inside the tasks environment:

documentclassarticle
usepackagetasks
usepackage[french]babel

usepackageetoolbox
AtBeginEnvironmenttaskscatcode`!12

begindocument

begintasks(3)
task aaa
task! fff
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

---

If you want to keep the active ! then you can use a more brute-force approach and change the character used to denote a full-line task. For instance with +:

documentclassarticle
usepackagetasks
usepackage[french]babel

ExplSyntaxOn
cs_gset_protected:Npn __tasks_read_item:www
 
 peek_meaning_remove:NTF + % <-- Character to activate a full-line task
 
 bool_set_true:N l__tasks_item_full_line_bool
 __tasks_read_item_aux:ww
 
 
 peek_meaning_remove:NTF *
 
 bool_set_true:N l__tasks_item_rest_of_line_bool
 __tasks_read_item_rest_of_line:ww
 
 __tasks_read_item_aux:ww 
 
 
ExplSyntaxOff

begindocument

begintasks(3)
task aaa
task+ fff
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

share|improve this answer

edited 24 mins ago

answered 53 mins ago

Phelype Oleinik

17.9k53871

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  unfortunately tasks seems to be gathering its contents because expandaftertaskstring! fails...
  – jfbu
  41 mins ago
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  and for same reason it seems impossible to use taskexclam in place of task! with taskexclam defined to expand to task <catcode twelve !>. So task package makes it hard to work around that problem if not using your approach which however has the problem that ! in items will not be correctly typeset for French.
  – jfbu
  36 mins ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  @jfbu Good point... Indeed, tasks uses environ's NewEnviron to collect the contents of the environment. It then uses peek_meaning_remove:NTF to check for the !. One would have to trick this test to get it working with the active !...
  – Phelype Oleinik
  27 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  maybe OP should send a Feature Request to tasks for either allow active ! or allow to specify another character for that job... or allow some taskfullwidth in place of task!.
  – jfbu
  18 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Thanks for your interest for this issue. I have opened an issue on the github page of the tasks package.
  – Colas
  5 mins ago
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f455050%2fincompatibility-between-babel-french-and-tasks%23new-answer', 'question_page');

);

Post as a guest

Name Email

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

active

oldest

votes

active

oldest

votes

up vote
3
down vote

I wouldn't call this "solving", but you can use etoolbox's AtBeginEnvironment hook to deactivate the ! inside the tasks environment:

documentclassarticle
usepackagetasks
usepackage[french]babel

usepackageetoolbox
AtBeginEnvironmenttaskscatcode`!12

begindocument

begintasks(3)
task aaa
task! fff
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

---

If you want to keep the active ! then you can use a more brute-force approach and change the character used to denote a full-line task. For instance with +:

documentclassarticle
usepackagetasks
usepackage[french]babel

ExplSyntaxOn
cs_gset_protected:Npn __tasks_read_item:www
 
 peek_meaning_remove:NTF + % <-- Character to activate a full-line task
 
 bool_set_true:N l__tasks_item_full_line_bool
 __tasks_read_item_aux:ww
 
 
 peek_meaning_remove:NTF *
 
 bool_set_true:N l__tasks_item_rest_of_line_bool
 __tasks_read_item_rest_of_line:ww
 
 __tasks_read_item_aux:ww 
 
 
ExplSyntaxOff

begindocument

begintasks(3)
task aaa
task+ fff
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

share|improve this answer

edited 24 mins ago

answered 53 mins ago

Phelype Oleinik

17.9k53871

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  unfortunately tasks seems to be gathering its contents because expandaftertaskstring! fails...
  – jfbu
  41 mins ago
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  and for same reason it seems impossible to use taskexclam in place of task! with taskexclam defined to expand to task <catcode twelve !>. So task package makes it hard to work around that problem if not using your approach which however has the problem that ! in items will not be correctly typeset for French.
  – jfbu
  36 mins ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  @jfbu Good point... Indeed, tasks uses environ's NewEnviron to collect the contents of the environment. It then uses peek_meaning_remove:NTF to check for the !. One would have to trick this test to get it working with the active !...
  – Phelype Oleinik
  27 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  maybe OP should send a Feature Request to tasks for either allow active ! or allow to specify another character for that job... or allow some taskfullwidth in place of task!.
  – jfbu
  18 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Thanks for your interest for this issue. I have opened an issue on the github page of the tasks package.
  – Colas
  5 mins ago
  

  
  
  
  

add a comment | 

up vote
3
down vote

I wouldn't call this "solving", but you can use etoolbox's AtBeginEnvironment hook to deactivate the ! inside the tasks environment:

documentclassarticle
usepackagetasks
usepackage[french]babel

usepackageetoolbox
AtBeginEnvironmenttaskscatcode`!12

begindocument

begintasks(3)
task aaa
task! fff
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

---

If you want to keep the active ! then you can use a more brute-force approach and change the character used to denote a full-line task. For instance with +:

documentclassarticle
usepackagetasks
usepackage[french]babel

ExplSyntaxOn
cs_gset_protected:Npn __tasks_read_item:www
 
 peek_meaning_remove:NTF + % <-- Character to activate a full-line task
 
 bool_set_true:N l__tasks_item_full_line_bool
 __tasks_read_item_aux:ww
 
 
 peek_meaning_remove:NTF *
 
 bool_set_true:N l__tasks_item_rest_of_line_bool
 __tasks_read_item_rest_of_line:ww
 
 __tasks_read_item_aux:ww 
 
 
ExplSyntaxOff

begindocument

begintasks(3)
task aaa
task+ fff
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

share|improve this answer

edited 24 mins ago

answered 53 mins ago

Phelype Oleinik

17.9k53871

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  unfortunately tasks seems to be gathering its contents because expandaftertaskstring! fails...
  – jfbu
  41 mins ago
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  and for same reason it seems impossible to use taskexclam in place of task! with taskexclam defined to expand to task <catcode twelve !>. So task package makes it hard to work around that problem if not using your approach which however has the problem that ! in items will not be correctly typeset for French.
  – jfbu
  36 mins ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  @jfbu Good point... Indeed, tasks uses environ's NewEnviron to collect the contents of the environment. It then uses peek_meaning_remove:NTF to check for the !. One would have to trick this test to get it working with the active !...
  – Phelype Oleinik
  27 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  maybe OP should send a Feature Request to tasks for either allow active ! or allow to specify another character for that job... or allow some taskfullwidth in place of task!.
  – jfbu
  18 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Thanks for your interest for this issue. I have opened an issue on the github page of the tasks package.
  – Colas
  5 mins ago
  

  
  
  
  

add a comment | 

up vote
3
down vote

up vote
3
down vote

I wouldn't call this "solving", but you can use etoolbox's AtBeginEnvironment hook to deactivate the ! inside the tasks environment:

documentclassarticle
usepackagetasks
usepackage[french]babel

usepackageetoolbox
AtBeginEnvironmenttaskscatcode`!12

begindocument

begintasks(3)
task aaa
task! fff
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

---

If you want to keep the active ! then you can use a more brute-force approach and change the character used to denote a full-line task. For instance with +:

documentclassarticle
usepackagetasks
usepackage[french]babel

ExplSyntaxOn
cs_gset_protected:Npn __tasks_read_item:www
 
 peek_meaning_remove:NTF + % <-- Character to activate a full-line task
 
 bool_set_true:N l__tasks_item_full_line_bool
 __tasks_read_item_aux:ww
 
 
 peek_meaning_remove:NTF *
 
 bool_set_true:N l__tasks_item_rest_of_line_bool
 __tasks_read_item_rest_of_line:ww
 
 __tasks_read_item_aux:ww 
 
 
ExplSyntaxOff

begindocument

begintasks(3)
task aaa
task+ fff
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

share|improve this answer

edited 24 mins ago

answered 53 mins ago

Phelype Oleinik

17.9k53871

I wouldn't call this "solving", but you can use etoolbox's AtBeginEnvironment hook to deactivate the ! inside the tasks environment:

documentclassarticle
usepackagetasks
usepackage[french]babel

usepackageetoolbox
AtBeginEnvironmenttaskscatcode`!12

begindocument

begintasks(3)
task aaa
task! fff
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

---

If you want to keep the active ! then you can use a more brute-force approach and change the character used to denote a full-line task. For instance with +:

documentclassarticle
usepackagetasks
usepackage[french]babel

ExplSyntaxOn
cs_gset_protected:Npn __tasks_read_item:www
 
 peek_meaning_remove:NTF + % <-- Character to activate a full-line task
 
 bool_set_true:N l__tasks_item_full_line_bool
 __tasks_read_item_aux:ww
 
 
 peek_meaning_remove:NTF *
 
 bool_set_true:N l__tasks_item_rest_of_line_bool
 __tasks_read_item_rest_of_line:ww
 
 __tasks_read_item_aux:ww 
 
 
ExplSyntaxOff

begindocument

begintasks(3)
task aaa
task+ fff
task bbb
task ccc
task ddd
task eee
endtasks

enddocument

share|improve this answer

edited 24 mins ago

answered 53 mins ago

Phelype Oleinik

17.9k53871

share|improve this answer

share|improve this answer

edited 24 mins ago

edited 24 mins ago

edited 24 mins ago

answered 53 mins ago

Phelype Oleinik

17.9k53871

answered 53 mins ago

Phelype Oleinik

17.9k53871

answered 53 mins ago

Phelype Oleinik

17.9k53871

17.9k53871

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  unfortunately tasks seems to be gathering its contents because expandaftertaskstring! fails...
  – jfbu
  41 mins ago
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  and for same reason it seems impossible to use taskexclam in place of task! with taskexclam defined to expand to task <catcode twelve !>. So task package makes it hard to work around that problem if not using your approach which however has the problem that ! in items will not be correctly typeset for French.
  – jfbu
  36 mins ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  @jfbu Good point... Indeed, tasks uses environ's NewEnviron to collect the contents of the environment. It then uses peek_meaning_remove:NTF to check for the !. One would have to trick this test to get it working with the active !...
  – Phelype Oleinik
  27 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  maybe OP should send a Feature Request to tasks for either allow active ! or allow to specify another character for that job... or allow some taskfullwidth in place of task!.
  – jfbu
  18 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Thanks for your interest for this issue. I have opened an issue on the github page of the tasks package.
  – Colas
  5 mins ago
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  unfortunately tasks seems to be gathering its contents because expandaftertaskstring! fails...
  – jfbu
  41 mins ago
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  and for same reason it seems impossible to use taskexclam in place of task! with taskexclam defined to expand to task <catcode twelve !>. So task package makes it hard to work around that problem if not using your approach which however has the problem that ! in items will not be correctly typeset for French.
  – jfbu
  36 mins ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  @jfbu Good point... Indeed, tasks uses environ's NewEnviron to collect the contents of the environment. It then uses peek_meaning_remove:NTF to check for the !. One would have to trick this test to get it working with the active !...
  – Phelype Oleinik
  27 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  maybe OP should send a Feature Request to tasks for either allow active ! or allow to specify another character for that job... or allow some taskfullwidth in place of task!.
  – jfbu
  18 mins ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Thanks for your interest for this issue. I have opened an issue on the github page of the tasks package.
  – Colas
  5 mins ago
  

  
  
  
  

1

1

unfortunately tasks seems to be gathering its contents because expandaftertaskstring! fails...
– jfbu
41 mins ago

unfortunately tasks seems to be gathering its contents because expandaftertaskstring! fails...
– jfbu
41 mins ago

1

1

and for same reason it seems impossible to use taskexclam in place of task! with taskexclam defined to expand to task <catcode twelve !>. So task package makes it hard to work around that problem if not using your approach which however has the problem that ! in items will not be correctly typeset for French.
– jfbu
36 mins ago

and for same reason it seems impossible to use taskexclam in place of task! with taskexclam defined to expand to task <catcode twelve !>. So task package makes it hard to work around that problem if not using your approach which however has the problem that ! in items will not be correctly typeset for French.
– jfbu
36 mins ago

1

1

@jfbu Good point... Indeed, tasks uses environ's NewEnviron to collect the contents of the environment. It then uses peek_meaning_remove:NTF to check for the !. One would have to trick this test to get it working with the active !...
– Phelype Oleinik
27 mins ago

@jfbu Good point... Indeed, tasks uses environ's NewEnviron to collect the contents of the environment. It then uses peek_meaning_remove:NTF to check for the !. One would have to trick this test to get it working with the active !...
– Phelype Oleinik
27 mins ago

maybe OP should send a Feature Request to tasks for either allow active ! or allow to specify another character for that job... or allow some taskfullwidth in place of task!.
– jfbu
18 mins ago

maybe OP should send a Feature Request to tasks for either allow active ! or allow to specify another character for that job... or allow some taskfullwidth in place of task!.
– jfbu
18 mins ago

Thanks for your interest for this issue. I have opened an issue on the github page of the tasks package.
– Colas
5 mins ago

Thanks for your interest for this issue. I have opened an issue on the github page of the tasks package.
– Colas
5 mins ago

add a comment | 

 

draft saved

draft discarded

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f455050%2fincompatibility-between-babel-french-and-tasks%23new-answer', 'question_page');

);

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Name Email

Name

Email

Name Email

Name

Email