| Summary: | Encoding problem editing apache config files | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | aungsan <mike.aungsan> |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | grave | Keywords: | triaged |
| Priority: | NOR | ||
| Version First Reported In: | 3.8.90 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | file to test | ||
|
Description
aungsan
2013-02-01 00:33:57 UTC
Please attach the file that works, and the one that does not work, otherwise we can't say what's going wrong: Is it the file content? Is it file permissions? If you can provide the information requested in comment #1, please add it. Created attachment 76995 [details]
file to test
Yes it is the file content.
I attach the file. apache need to install sudo apt-get install apache.
Please follow step 1. 2. 3.
There is not working file and non-working file. When file is edited with kate, apache can no longer understand its configuration file.
If I edit the file as you describe (insert or remove a <tab>), the content equals except on the line I changed (using vimdiff or kompare). So to me it looks like the content is not broken. Possible problems: 1. make sure the file permissions are correct 2. make sure the document encoding is correct That is true. Nothing seem wrong. But when I restart Apache service it could not restart it. It is encoding problem. On Fri, Feb 8, 2013 at 1:47 AM, Dominik Haumann <dhaumann@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=314225 > > --- Comment #4 from Dominik Haumann <dhaumann@kde.org> --- > If I edit the file as you describe (insert or remove a <tab>), the content > equals except on the line I changed (using vimdiff or kompare). So to me it > looks like the content is not broken. > > Possible problems: > 1. make sure the file permissions are correct > 2. make sure the document encoding is correct > > -- > You are receiving this mail because: > You reported the bug. > @aungsan: so if it is an encoding problem, this report can be closed right? The encoding detection works as good as possible, so I fear we cannot do anything about it. 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 set the bug status 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! Dear Bug Submitter, 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! |