Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Have a nested task number in work package #47

Open
ansjin opened this issue Mar 1, 2020 · 3 comments
Open

Have a nested task number in work package #47

ansjin opened this issue Mar 1, 2020 · 3 comments

Comments

@ansjin
Copy link

ansjin commented Mar 1, 2020

Hello,

Currently, in the proposal, the task number is initialized to 1.1 whenever a new work package is started.
For example, package 3.1, tasks will be numbered as 1.1, 1.2, etc.

Is there a way by which it can have a nesting numbering like for work package 3.1, the tasks have numbering like 3.1.1, 3.1.2, etc.

@kohlhase
Copy link
Member

kohlhase commented Mar 2, 2020

It would be relatively easy to do this. I am not clear what the user interface would be. I see there could be an option deeptasklabels for the package, or a key for the proposal environment, or the workpackage environment.

I am not sure what is best.

@ansjin
Copy link
Author

ansjin commented Mar 2, 2020

Hello @kohlhase,

I am currently using dfgproposal class like this:
\documentclass[submit, numericcites]{dfgproposal}
It is similar in structure as here: https://github.com/KWARC/LaTeX-proposal/tree/master/examples/dfg/proposal

I added both key and deeptasklabels but it didn't work:
\documentclass[submit, numericcites,key, deeptasklabels]{dfgproposal}

I also tried with longtasklabels:
\documentclass[submit,longtasklabels, numericcites]{dfgproposal}

Is there any other way? or I am doing something wrong?

@kohlhase
Copy link
Member

kohlhase commented Mar 2, 2020

Sorry, you misunderstood. I was speculating about what the user interface should look like.
In any case, the extended labels will have to be implemented (easy) but they need to be turn-offable (therefore we need to understand at what level you want to select the extended labels).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants