[Dltk-dev] Encoding issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[Dltk-dev] Encoding issues

From: Renato Silva <br.renatosilva@xxxxxxxxx>
Date: Sun, 31 May 2009 23:54:18 -0300
Delivered-to: dltk-dev@xxxxxxxxxxx
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=f57VEnhlNn2TQ+oc19JIAuCHerx0sfPxjhZ+AZhfwDaDhrHByWUbHoWjZ9tIwI3iEw 05B515UM65eGe1dBZzr5n6/g6VZtWrbHJmF08FaKY9lWYWnsy0jdFmm/lHebkYW2uTja 6F9Yna/AOZAPcqP2OHmAnDUfnKA56k+tdZDy8=
List-archive: <https://dev.eclipse.org/mailman/private/dltk-dev>
List-help: <mailto:dltk-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/dltk-dev>, <mailto:dltk-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/dltk-dev>, <mailto:dltk-dev-request@eclipse.org?subject=unsubscribe>

Can anyone please give me any feedback about these bugs?

Are they out-of-date or no work on them yet? It seems that currently it's just a matter of displaying the right encoding in file properties. For example, I have iso-8859-1 files, but DLTK Ruby stands they are utf-8 determined by content.

http://bugs.eclipse.org/238945

http://bugs.eclipse.org/239082

As I've heard that DLTK 1.0 will be released together with Galileo, and as not everyone works with UTF-8 only (including me), I think these reports are worth attention.

Sorry if I'm disturbing.

Prev by Date: [Dltk-dev] Multi-sourcefile and code-completion problems
Next by Date: [Dltk-dev] [BUILD] S-1.0RC3-200906021143
Previous by thread: [Dltk-dev] Multi-sourcefile and code-completion problems
Next by thread: [Dltk-dev] [BUILD] S-1.0RC3-200906021143
Index(es):
- Date
- Thread

Breadcrumbs