add documentation of function RAWSUBTRACK
I guess you mean RAWSUBTRACT ???
Is this open for anyone? Are any pointers for this bug available, please?
Yes, it's open as assignee is not set.
You have two options to solve this bug:
1. Write the Help content in plain text and the documentation team will convert it to XHP files.
2. You can directly edit the XHP files (XML format). See an example of adding help for a function here:
For that, you need:
- to create a new file in text/scalc/01 (the Help Authoring extension is the best option how to do that),
- to add this file to makefile,
- to embed this file into the list of functions. I assume RAWSUBTRACT should go to the mathematical functions, i.e. to the file text/scalc/01/04060106.xhp
CC to Olivier: if I forgot anything, please complete my instructions.
If you want it done quickly then better write a document with the contents. See other Calc function on what to put inside. Examples and corner cases described are welcome.
Then attach it here and one of us will transform into a help file.
Directly editing the XML files is tricky and subject to mistakes. But if you want to jump help editing, let us know.
I have submitted a Draft on Gerrit. I have added Olivier as a reviewer. Is this correct? I'm sorry if I made a mistake somewhere but I'm totally new to Gerrit.
liongold committed a patch related to this issue.
It has been pushed to "master":
tdf#101140 Adding Help for RAWSUBTRACT function
Sorry again for the question. I understand that master will be used for the post-5.3 release (5.4 I guess). Can someone guide me if help content changes can be added to LibreOffice 5.3 (since it's still not announced officially) or 5.2? I'm sorry if this is a stupid question. Thank you for your patience.
Is this bug fixed?
If so, could you please close it as RESOLVED FIXED?
Ok, will do and sorry for not doing this earlier. However, I was waiting for a reply on whether this change should have been ported to previous versions (5.2 and 5.3 - I guess the question does not have sense because 5.3 is close to be out now I think).
(In reply to beimaginativeegroup from comment #10)
> Ok, will do and sorry for not doing this earlier. However, I was waiting for
> a reply on whether this change should have been ported to previous versions
Updates to help involve changing translatable strings, which is blocked by our string freeze policy, so no: just fixing it in master is OK.