After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 351163 - Default encoding should be should have translator comment
Default encoding should be should have translator comment
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: I18N
git master
Other All
: Normal minor
: gnome-2-24
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-13 15:16 UTC by Baris Cicek
Modified: 2008-11-15 20:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Add translator comment in schemas file (648 bytes, patch)
2008-10-03 20:27 UTC, Claude Paroz
committed Details | Review

Description Baris Cicek 2006-08-13 15:16:31 UTC
On epiphany po file there's no comment for default encoding entry. It's just used as ISO-8859-1 and translator has not information about if s/he should change this string. This entry is coming from epiphany.schemas.in.h (line 21)

Other information:
Epiphany maybe should use utf-8 as a default encoding. And english translation should change this to iso-8859-1 if they need to.
Comment 1 Diego Escalante Urrelo (not reading bugmail) 2006-12-26 09:38:57 UTC
Just checked:

diego@milkyway:~/gnome/epiphany/epiphany/po$ grep charset\= *.po|grep -v UTF
am.po:"Content-Type: text/plain; charset=utf-8\n"
is.po:"Content-Type: text/plain; charset=utf-8\n"
** I understand that the charset is not case sensitive


diego@milkyway:~/gnome/epiphany/epiphany/po$ file *.po 
am.po:      UTF-8 Unicode English text
ar.po:      UTF-8 Unicode English text
az.po:      UTF-8 Unicode English text
be.po:      UTF-8 Unicode PO (gettext message catalogue) text
bg.po:      UTF-8 Unicode English text
bn_IN.po:   UTF-8 Unicode English text
bn.po:      UTF-8 Unicode English text
bs.po:      UTF-8 Unicode English text
ca.po:      UTF-8 Unicode English text
cs.po:      UTF-8 Unicode English text
cy.po:      UTF-8 Unicode PO (gettext message catalogue) text
da.po:      UTF-8 Unicode English text
de.po:      UTF-8 Unicode PO (gettext message catalogue) text
dz.po:      UTF-8 Unicode English text, with very long lines
el.po:      UTF-8 Unicode English text
en_CA.po:   UTF-8 Unicode English text
en_GB.po:   UTF-8 Unicode English text, with very long lines
es.po:      UTF-8 Unicode English text
et.po:      UTF-8 Unicode English text, with very long lines
eu.po:      UTF-8 Unicode English text
fa.po:      UTF-8 Unicode English text
fi.po:      UTF-8 Unicode English text
fr.po:      UTF-8 Unicode English text
ga.po:      UTF-8 Unicode English text
gl.po:      UTF-8 Unicode English text
gu.po:      UTF-8 Unicode PO (gettext message catalogue) text
he.po:      UTF-8 Unicode English text
hi.po:      UTF-8 Unicode English text
hr.po:      UTF-8 Unicode PO (gettext message catalogue) text
hu.po:      UTF-8 Unicode English text
id.po:      UTF-8 Unicode English text
is.po:      UTF-8 Unicode English text
it.po:      UTF-8 Unicode English text
ja.po:      UTF-8 Unicode PO (gettext message catalogue) text
ka.po:      UTF-8 Unicode English text
ko.po:      UTF-8 Unicode PO (gettext message catalogue) text
ku.po:      UTF-8 Unicode English text, with very long lines
li.po:      UTF-8 Unicode PO (gettext message catalogue) text
lt.po:      UTF-8 Unicode English text
lv.po:      UTF-8 Unicode English text
mg.po:      UTF-8 Unicode English text
mi.po:      UTF-8 Unicode English text
mk.po:      UTF-8 Unicode English text
ml.po:      UTF-8 Unicode English text
mn.po:      UTF-8 Unicode English text
mr.po:      UTF-8 Unicode English text
ms.po:      ASCII PO (gettext message catalogue) text
nb.po:      UTF-8 Unicode PO (gettext message catalogue) text
ne.po:      UTF-8 Unicode English text
nl.po:      UTF-8 Unicode PO (gettext message catalogue) text
nn.po:      UTF-8 Unicode English text
or.po:      UTF-8 Unicode English text
pa.po:      UTF-8 Unicode English text
pl.po:      UTF-8 Unicode PO (gettext message catalogue) text
pt_BR.po:   UTF-8 Unicode English text
pt.po:      UTF-8 Unicode English text
ro.po:      UTF-8 Unicode PO (gettext message catalogue) text
ru.po:      UTF-8 Unicode PO (gettext message catalogue) text
rw.po:      UTF-8 Unicode English text
sk.po:      UTF-8 Unicode English text
sl.po:      UTF-8 Unicode English text, with very long lines
sq.po:      UTF-8 Unicode English text
sr@Latn.po: UTF-8 Unicode English text
sr.po:      UTF-8 Unicode English text
sv.po:      UTF-8 Unicode PO (gettext message catalogue) text, with very long lines
ta.po:      UTF-8 Unicode English text
te.po:      UTF-8 Unicode English text
th.po:      UTF-8 Unicode English text
tk.po:      UTF-8 Unicode English text
tr.po:      UTF-8 Unicode English text
uk.po:      UTF-8 Unicode English text
vi.po:      UTF-8 Unicode PO (gettext message catalogue) text
wa.po:      UTF-8 Unicode English text
zh_CN.po:   UTF-8 Unicode English text
zh_HK.po:   UTF-8 Unicode PO (gettext message catalogue) text
zh_TW.po:   UTF-8 Unicode PO (gettext message catalogue) text


** Only the ms translation is read as ASCII, seems like they do not use any non ascii symbol?.

I think this was fixed or never was a problem or maybe I didn't get the idea. But I vote for closing this.
Comment 2 Christian Persch 2006-12-26 19:07:47 UTC
This is about the gconf key in the schemas file.
Comment 3 Christian Persch 2007-03-12 12:25:25 UTC
Moving to 2.20 target due to feature and UI freeze for 2.18.
Comment 4 Baris Cicek 2007-03-12 14:25:10 UTC
This is not a translation bug, neither UI bug. That's about default preferences of epiphany. 

Issue is, epiphany is using default charset from schemas.in by default. And it seems like default charset is marked to be translated in schems.in.h. 

However it's not obvious for a translator to understand that that line (in epiphany.schemas.in.h:21) is for default charset while browsing the web. 

Currently it should be set to UTF-8 for most of the languages, as we use it by default on our web pages as well. 

That's what this bug is about. An easy possible fix is to add a translation comment (if possible) to epiphany.schemas.in.h, so that translator will get informed about that's where s/he should set default encoding.
Comment 5 Claude Paroz 2008-10-03 20:27:24 UTC
Created attachment 119885 [details] [review]
Add translator comment in schemas file

The comment must be inside the "default" tag.
Comment 6 Claude Paroz 2008-11-15 20:58:02 UTC
Committed in trunk