Hi Kosyrev, 2015ko azaroak 10an, Kosyrev Serge-ek idatzi zuen: > Perhaps I was unclear in this message -- it's not the Org's priority > mechanism that is broken, it's the way ox-taskjuggler uses it that is. > > Org specifies priorities via a list of enums, whereas TJ expects an > integer in the range 0-1000. > > The quoted little piece of math in ox-taskjuggler tried to provide a > mapping, but failed and I couldn't figure out how to make it work -- > mainly because I couldn't understand how it was /supposed/ to work.
Org priorities are expressed as single characters (conventionally uppercase Latin letters). These map to ASCII/Unicode code points (i.e. integers). The code interpolates these values linearly between 0 and 1000. By default org has three priorities A, B, and C; these map to 1000, 500, and 0 respectively. Five priorities A through E would map to 1000, 750, 500, 250, and 0. Etc. The letter/integer substitution is a bit opaque. So is the fact that org-lowest-priority (by default the ASCII codepoint for āCā = 67) is a larger integer than org-highest-priority (ASCII āAā = 65), despite what the names suggest. Does that help any? -- Aaron Ecay