* encoding problem
@ 2012-05-30 9:55 Julien Cubizolles
2012-05-30 16:29 ` Bernt Hansen
0 siblings, 1 reply; 8+ messages in thread
From: Julien Cubizolles @ 2012-05-30 9:55 UTC (permalink / raw)
To: emacs-orgmode
I'm having a very strange problem with character encoding. I write all
my text files with emacs, with non-ascii characters (I'm french). I keep
a copy of many files (latex/org/...) on separate machines using
unison. Very often after a synchronization, the non-ascii charaters are
completely displayed wrong (à for à, ç for ç) in the org files, but
never in the latex files.
I guess it's more an Emacs than org files but I can't see what's special
in the org files that makes them more prone to such errors.
Is there a way to *fix* easily these corruptions on a file, ie searching
for all "weird" characters to replace ?
How could I prevent this from happening again (checking/changing
character encoding maybe ?)
Thanks for your help,
Julien.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: encoding problem
2012-05-30 9:55 encoding problem Julien Cubizolles
@ 2012-05-30 16:29 ` Bernt Hansen
2012-06-01 8:16 ` Eric S Fraga
0 siblings, 1 reply; 8+ messages in thread
From: Bernt Hansen @ 2012-05-30 16:29 UTC (permalink / raw)
To: Julien Cubizolles; +Cc: emacs-orgmode
Julien Cubizolles <j.cubizolles@free.fr> writes:
> I'm having a very strange problem with character encoding. I write all
> my text files with emacs, with non-ascii characters (I'm french). I keep
> a copy of many files (latex/org/...) on separate machines using
> unison. Very often after a synchronization, the non-ascii charaters are
> completely displayed wrong (à for à, ç for ç) in the org files, but
> never in the latex files.
>
> I guess it's more an Emacs than org files but I can't see what's special
> in the org files that makes them more prone to such errors.
>
> Is there a way to *fix* easily these corruptions on a file, ie searching
> for all "weird" characters to replace ?
>
> How could I prevent this from happening again (checking/changing
> character encoding maybe ?)
>
> Thanks for your help,
>
> Julien.
Hi Julien,
I get prompts for encoding when saving/exporting (on Windows only) so I
put the following at the top of my org-files
--8<---------------cut here---------------start------------->8---
# -*- coding: utf-8 -*-
--8<---------------cut here---------------end--------------->8---
which seems to fix the problem for me. Maybe this will help?
Bernt
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: encoding problem
2012-05-30 16:29 ` Bernt Hansen
@ 2012-06-01 8:16 ` Eric S Fraga
2012-06-01 16:15 ` Bernt Hansen
2012-06-02 8:49 ` Julien Cubizolles
0 siblings, 2 replies; 8+ messages in thread
From: Eric S Fraga @ 2012-06-01 8:16 UTC (permalink / raw)
To: Bernt Hansen; +Cc: emacs-orgmode, Julien Cubizolles
Bernt Hansen <bernt@norang.ca> writes:
> Julien Cubizolles <j.cubizolles@free.fr> writes:
>
>> I'm having a very strange problem with character encoding. I write all
>> my text files with emacs, with non-ascii characters (I'm french). I keep
>> a copy of many files (latex/org/...) on separate machines using
>> unison. Very often after a synchronization, the non-ascii charaters are
>> completely displayed wrong (à for à, ç for ç) in the org files, but
>> never in the latex files.
>>
>> I guess it's more an Emacs than org files but I can't see what's special
>> in the org files that makes them more prone to such errors.
>>
>> Is there a way to *fix* easily these corruptions on a file, ie searching
>> for all "weird" characters to replace ?
>>
>> How could I prevent this from happening again (checking/changing
>> character encoding maybe ?)
>>
>> Thanks for your help,
>>
>> Julien.
>
> Hi Julien,
>
> I get prompts for encoding when saving/exporting (on Windows only) so I
> put the following at the top of my org-files
>
> # -*- coding: utf-8 -*-
>
> which seems to fix the problem for me. Maybe this will help?
I used to have this problem and it was incredibly annoying. I also
started adding the line Bernt suggests but I kept forgetting for new
files. I finally solved this problem by adding the following lines to
my emacs initialisation:
#+begin_src emacs-lisp
(prefer-coding-system 'utf-8)
(set-charset-priority 'unicode)
(setq default-process-coding-system '(utf-8-unix . utf-8-unix))
#+end_src
I couldn't tell you which of these matter or whether they are all
necessary but I don't have these problems any longer so I haven't
investigated any further!
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.10-630-g4144c5.dirty
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: encoding problem
2012-06-01 8:16 ` Eric S Fraga
@ 2012-06-01 16:15 ` Bernt Hansen
2012-06-01 16:31 ` Nick Dokos
2012-06-02 8:49 ` Julien Cubizolles
1 sibling, 1 reply; 8+ messages in thread
From: Bernt Hansen @ 2012-06-01 16:15 UTC (permalink / raw)
To: Eric S Fraga; +Cc: emacs-orgmode, Julien Cubizolles
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Bernt Hansen <bernt@norang.ca> writes:
>
>> Julien Cubizolles <j.cubizolles@free.fr> writes:
>>
>>> I'm having a very strange problem with character encoding. I write all
>>> my text files with emacs, with non-ascii characters (I'm french). I keep
>>> a copy of many files (latex/org/...) on separate machines using
>>> unison. Very often after a synchronization, the non-ascii charaters are
>>> completely displayed wrong (à for à, ç for ç) in the org files, but
>>> never in the latex files.
>>>
>>> I guess it's more an Emacs than org files but I can't see what's special
>>> in the org files that makes them more prone to such errors.
>>>
>>> Is there a way to *fix* easily these corruptions on a file, ie searching
>>> for all "weird" characters to replace ?
>>>
>>> How could I prevent this from happening again (checking/changing
>>> character encoding maybe ?)
>>>
>>> Thanks for your help,
>>>
>>> Julien.
>>
>> Hi Julien,
>>
>> I get prompts for encoding when saving/exporting (on Windows only) so I
>> put the following at the top of my org-files
>>
>> # -*- coding: utf-8 -*-
>>
>> which seems to fix the problem for me. Maybe this will help?
>
> I used to have this problem and it was incredibly annoying. I also
> started adding the line Bernt suggests but I kept forgetting for new
> files. I finally solved this problem by adding the following lines to
> my emacs initialisation:
>
> #+begin_src emacs-lisp
> (prefer-coding-system 'utf-8)
> (set-charset-priority 'unicode)
> (setq default-process-coding-system '(utf-8-unix . utf-8-unix))
> #+end_src
>
> I couldn't tell you which of these matter or whether they are all
> necessary but I don't have these problems any longer so I haven't
> investigated any further!
Thanks Eric!
I'll try this and drop my mode line setting in each org file. I still
encounter this when archiving for the first time to a new file -- since
I'm archive utf-8 content and the new target org file prompts for
encoding with my current setup.
Regards,
Bernt
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: encoding problem
2012-06-01 16:15 ` Bernt Hansen
@ 2012-06-01 16:31 ` Nick Dokos
2012-06-01 18:20 ` Bernt Hansen
0 siblings, 1 reply; 8+ messages in thread
From: Nick Dokos @ 2012-06-01 16:31 UTC (permalink / raw)
To: Bernt Hansen; +Cc: emacs-orgmode, Julien Cubizolles
Bernt Hansen <bernt@norang.ca> wrote:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
> > Bernt Hansen <bernt@norang.ca> writes:
> >
> >> Julien Cubizolles <j.cubizolles@free.fr> writes:
> >>
> >>> I'm having a very strange problem with character encoding. I write all
> >>> my text files with emacs, with non-ascii characters (I'm french). I keep
> >>> a copy of many files (latex/org/...) on separate machines using
> >>> unison. Very often after a synchronization, the non-ascii charaters are
> >>> completely displayed wrong (à for à, ç for ç) in the org files, but
> >>> never in the latex files.
> >>>
> >>> I guess it's more an Emacs than org files but I can't see what's special
> >>> in the org files that makes them more prone to such errors.
> >>>
> >>> Is there a way to *fix* easily these corruptions on a file, ie searching
> >>> for all "weird" characters to replace ?
> >>>
> >>> How could I prevent this from happening again (checking/changing
> >>> character encoding maybe ?)
> >>>
> >>> Thanks for your help,
> >>>
> >>> Julien.
> >>
> >> Hi Julien,
> >>
> >> I get prompts for encoding when saving/exporting (on Windows only) so I
> >> put the following at the top of my org-files
> >>
> >> # -*- coding: utf-8 -*-
> >>
> >> which seems to fix the problem for me. Maybe this will help?
> >
> > I used to have this problem and it was incredibly annoying. I also
> > started adding the line Bernt suggests but I kept forgetting for new
> > files. I finally solved this problem by adding the following lines to
> > my emacs initialisation:
> >
> > #+begin_src emacs-lisp
> > (prefer-coding-system 'utf-8)
> > (set-charset-priority 'unicode)
> > (setq default-process-coding-system '(utf-8-unix . utf-8-unix))
> > #+end_src
> >
> > I couldn't tell you which of these matter or whether they are all
> > necessary but I don't have these problems any longer so I haven't
> > investigated any further!
>
> Thanks Eric!
>
> I'll try this and drop my mode line setting in each org file. I still
> encounter this when archiving for the first time to a new file -- since
> I'm archive utf-8 content and the new target org file prompts for
> encoding with my current setup.
>
> Regards,
> Bernt
Isn't the setting of LANG used during initialization to set these things?
I have LANG set to en_US.UTF-8 and new buffers are in utf-8-unix
(except for mail composition buffers: they are in undecided-unix).
I'm pretty sure I'm not mucking with coding systems anywhere in my emacs
initialization otherwise.
Nick
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: encoding problem
2012-06-01 16:31 ` Nick Dokos
@ 2012-06-01 18:20 ` Bernt Hansen
2012-06-01 18:35 ` Nick Dokos
0 siblings, 1 reply; 8+ messages in thread
From: Bernt Hansen @ 2012-06-01 18:20 UTC (permalink / raw)
To: nicholas.dokos; +Cc: emacs-orgmode, Julien Cubizolles
Nick Dokos <nicholas.dokos@hp.com> writes:
> Bernt Hansen <bernt@norang.ca> wrote:
>
>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>>
>> > Bernt Hansen <bernt@norang.ca> writes:
>> >
>> >> Julien Cubizolles <j.cubizolles@free.fr> writes:
>> >>
>> >>> I'm having a very strange problem with character encoding. I write all
>> >>> my text files with emacs, with non-ascii characters (I'm french). I keep
>> >>> a copy of many files (latex/org/...) on separate machines using
>> >>> unison. Very often after a synchronization, the non-ascii charaters are
>> >>> completely displayed wrong (à for à, ç for ç) in the org files, but
>> >>> never in the latex files.
>> >>>
>> >>> I guess it's more an Emacs than org files but I can't see what's special
>> >>> in the org files that makes them more prone to such errors.
>> >>>
>> >>> Is there a way to *fix* easily these corruptions on a file, ie searching
>> >>> for all "weird" characters to replace ?
>> >>>
>> >>> How could I prevent this from happening again (checking/changing
>> >>> character encoding maybe ?)
>> >>>
>> >>> Thanks for your help,
>> >>>
>> >>> Julien.
>> >>
>> >> Hi Julien,
>> >>
>> >> I get prompts for encoding when saving/exporting (on Windows only) so I
>> >> put the following at the top of my org-files
>> >>
>> >> # -*- coding: utf-8 -*-
>> >>
>> >> which seems to fix the problem for me. Maybe this will help?
>> >
>> > I used to have this problem and it was incredibly annoying. I also
>> > started adding the line Bernt suggests but I kept forgetting for new
>> > files. I finally solved this problem by adding the following lines to
>> > my emacs initialisation:
>> >
>> > #+begin_src emacs-lisp
>> > (prefer-coding-system 'utf-8)
>> > (set-charset-priority 'unicode)
>> > (setq default-process-coding-system '(utf-8-unix . utf-8-unix))
>> > #+end_src
>> >
>> > I couldn't tell you which of these matter or whether they are all
>> > necessary but I don't have these problems any longer so I haven't
>> > investigated any further!
>>
>> Thanks Eric!
>>
>> I'll try this and drop my mode line setting in each org file. I still
>> encounter this when archiving for the first time to a new file -- since
>> I'm archive utf-8 content and the new target org file prompts for
>> encoding with my current setup.
>>
>> Regards,
>> Bernt
>
> Isn't the setting of LANG used during initialization to set these things?
> I have LANG set to en_US.UTF-8 and new buffers are in utf-8-unix
> (except for mail composition buffers: they are in undecided-unix).
> I'm pretty sure I'm not mucking with coding systems anywhere in my emacs
> initialization otherwise.
>
> Nick
Maybe - I'm having this issue on Windows...
-Bernt
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: encoding problem
2012-06-01 18:20 ` Bernt Hansen
@ 2012-06-01 18:35 ` Nick Dokos
0 siblings, 0 replies; 8+ messages in thread
From: Nick Dokos @ 2012-06-01 18:35 UTC (permalink / raw)
To: Bernt Hansen; +Cc: emacs-orgmode, Julien Cubizolles
Bernt Hansen <bernt@norang.ca> wrote:
> Nick Dokos <nicholas.dokos@hp.com> writes:
>
> > Isn't the setting of LANG used during initialization to set these things?
> > I have LANG set to en_US.UTF-8 and new buffers are in utf-8-unix
> > (except for mail composition buffers: they are in undecided-unix).
> > I'm pretty sure I'm not mucking with coding systems anywhere in my emacs
> > initialization otherwise.
> >
> > Nick
>
>
> Maybe - I'm having this issue on Windows...
>
Ah - OK: forgive my parochialism. I guess the question is whether
whatever version of emacs you are using can access the locale
information on Windows and do the equivalent of what it does on POSIX-y
systems.
Nick
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: encoding problem
2012-06-01 8:16 ` Eric S Fraga
2012-06-01 16:15 ` Bernt Hansen
@ 2012-06-02 8:49 ` Julien Cubizolles
1 sibling, 0 replies; 8+ messages in thread
From: Julien Cubizolles @ 2012-06-02 8:49 UTC (permalink / raw)
To: emacs-orgmode
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> I used to have this problem and it was incredibly annoying. I also
> started adding the line Bernt suggests but I kept forgetting for new
> files. I finally solved this problem by adding the following lines to
> my emacs initialisation:
>
> #+begin_src emacs-lisp
> (prefer-coding-system 'utf-8)
> (set-charset-priority 'unicode)
> (setq default-process-coding-system '(utf-8-unix . utf-8-unix))
> #+end_src
I'll give it a try, thanks for your suggestion. I think my encoding
problems come from the many copy-paste I made from web pages (wikipedia
mostly) to org-files. I didn't think it would mess anything since
wikipedia pages are encoded in utf-8, or so I thought.
Julien.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2012-06-02 8:50 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-30 9:55 encoding problem Julien Cubizolles
2012-05-30 16:29 ` Bernt Hansen
2012-06-01 8:16 ` Eric S Fraga
2012-06-01 16:15 ` Bernt Hansen
2012-06-01 16:31 ` Nick Dokos
2012-06-01 18:20 ` Bernt Hansen
2012-06-01 18:35 ` Nick Dokos
2012-06-02 8:49 ` Julien Cubizolles
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).