Summary: | word count is counting wrong | ||
---|---|---|---|
Product: | [Applications] kile | Reporter: | Simon <SirTwist> |
Component: | general | Assignee: | Michel Ludwig <michel.ludwig> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | cruzki123 |
Priority: | NOR | ||
Version: | trunk-kde4 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Simon
2007-09-18 01:33:21 UTC
Hello, well it is not very accurate but that is because of the way latex works. Consider e.g. two cases: 1.) \usepackage{graphicx} this should not be counted as one word. 2.) but \textbf{stuff} should be counted as one word. But how should kile know if the stuff in brakets are real words or only options? A hardcoded list of latex commands would be a lot of work and will also fail as soon as you start to use newcommands. If you got any ideas how to reliable improve it, don't hesitate to tell us. Thomas PS: I'm not sure which ps/pdf viewers have a reliable word count. If I would known something then I would told you, but its not that easy. even other methods like: creating the pdf then pdftotext and then wc arent that good especially if you have a ToC with dots (every dot is counted as a word). I think there is no easy way to implement this. But there are some geniuses out there perhaps they can help. I thought a little about it, perhaps a blacklist with the ability to add new regular expressions would do the job. e.g. a list at the statistic window where I can add(or enable/disable) something like: - \begin{.*} - \end{*} or even something complexer: - \begin{tikzpicture}*\end{tikzpicture} and then the counter will ignore everything which matches those reg. exp. This is the best way which I can think of this far. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |