Tracker for translation requirements

[GoogleCodeExporter]

This bug will contain translation requirements as they come up. If you have 
time to help translate DashClock into another language—in which case, thank 
you VERY much—please star this issue to stay aware of new strings that need 
translating.

See http://code.google.com/p/dashclock/wiki/Translation for more info.

Original issue reported on code.google.com by roman.nurik on 17 Feb 2013 at 7:10

[GoogleCodeExporter]

Original comment by roman.nurik on 17 Feb 2013 at 7:33

• Added labels: Component-Translation

[GoogleCodeExporter]

Hi everyone, two translation strings were added today:

<string name="no_location_data">Your location could not be determined</string>
<string name="get_more_extensions">Get more extensions</string>

If you have a chance to provide translations, please comment in the original 
bug reports or pull requests for your language. Also, in the future I'll try to 
minimize the number of comments like this one and instead just send out a list 
of new strings a few days before publishing a new version of the app.

Original comment by roman.nurik on 18 Feb 2013 at 7:14

[GoogleCodeExporter]

Hi again everyone! I've started merging in more translations and I think the 
strings for 1.3 are pretty much complete.

Here are the missing strings along with languages:

pref_strings.xml:
-----------------
pref_clock_shortcut_title   pl, zh-rCN, zh-rTW
pref_shortcut_title pl, zh-rCN, zh-rTW
pref_shortcut_default   pl, zh-rCN, zh-rTW
pref_calendar_look_ahead_hours_title    cs
pref_calendar_look_ahead_hours_display_names    cs
pref_calendar_selected_title    cs, de, es, fr, it, ko, ru, zh-rCN, zh-rTW
pref_calendar_custom_visibility_title   cs, de, es, fr, it, ko, ru, zh-rCN, zh-rTW
pref_calendar_custom_visibility_description cs, de, es, fr, it, ko, ru, zh-rCN, 
zh-rTW

strings.xml:
------------
title_apps  pl, zh-rCN, zh-rTW
title_shortcuts pl, zh-rCN, zh-rTW
get_more_extensions de, fr, pl, ru
no_location_data    de, fr, pl, ru
title_calendar_settings cs

Original comment by roman.nurik on 18 Feb 2013 at 6:34

[GoogleCodeExporter]

Original comment by roman.nurik on 18 Feb 2013 at 6:54

• Changed state: Active

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I don't know how push my translations then i push here...

pref_strings.xml spanish translation

Original comment by david...@gmail.com on 18 Feb 2013 at 7:00

[GoogleCodeExporter]

@david: It's ok to attach the xml here.
Thanks for the work :)

Original comment by maca...@gmail.com on 18 Feb 2013 at 7:01

[GoogleCodeExporter]

Thanks David! In the future, please just comment on the translations tracker 
for your language:

http://code.google.com/p/dashclock/issues/list?can=1&q=Type%3DTracker+Component%
3DTranslation

For Spanish, it's issue 49.

Just wanted to keep the noise level down on this issue :)

Original comment by roman.nurik on 18 Feb 2013 at 7:06

[GoogleCodeExporter]

Hey Roman, seems like you've forgotten the 
pref_calendar_selected_summary_template plurals in the pref_strings.xml file, 
at least for me (Italian).

Original comment by pog...@gmail.com on 18 Feb 2013 at 7:37

[GoogleCodeExporter]

Hello Roman Nurik,

Missing Korean translations are added, please see issue 129.

Original comment by k@efir.uz on 19 Feb 2013 at 1:37

[GoogleCodeExporter]

Why not use crowd translation? For example with http://www.getlocalization.com/

Original comment by kirill.r...@gmail.com on 21 Feb 2013 at 1:57

[GoogleCodeExporter]

#11: May do that in the future.

Original comment by roman.nurik on 21 Feb 2013 at 2:04

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi all, I added a few new strings today (see below). If you're still interested 
in helping to translate, please take a look at the pref_strings.xml and 
strings.xml files for your language. You'll notice that the new requested 
strings are commented out — they're placeholders for the actual translations.

If you can translate the new strings, please comment on the relevant 
translation tracker issue for your language with either the new strings in a 
comment, a file attachment, or a pointer to commits in your clone/fork of the 
main repository.

PLEASE DO NOT COMMENT ON THIS ISSUE if you have questions — please post 
questions as comments in the issue relevant to your language.

Thanks!

New strings:

    <string name="pref_hide_settings_title">Hide settings button</string>
    <string name="pref_hide_settings_description">Hide the configuration button when the widget is vertically expanded (a "Configure DashClock Widget" home screen shortcut is available as an alternative)</string>

    <string name="pref_calendar_show_all_day_title">Show all-day events</string>
    <string name="pref_calendar_show_all_day_description">Include all-day events such as birthdays</string>

    <string name="today">Today</string>

Original comment by roman.nurik on 26 Feb 2013 at 5:21

[GoogleCodeExporter]

Hi all! It's been a while, and sorry for the delays in getting some of your 
translated strings added. As always, thanks for contributing.

I believe I've merged all the latest strings for already-added languages; they 
should make it into v1.5. There are still some kinks to work out with new 
languages, so I've not committed them yet and unfortunately I won't be adding 
new languages until probably v1.5.1.

Having said all that, here's the latest report on missing strings across all 
languages. There's more related to quantity strings (<plurals> elements) but 
those are lower priority. If you have time to help translate, please take a 
look below and provide an update on the translation tracker issue page for your 
language. Again, I really appreciate the help :)

res/values/strings.xml:32: "shortcut_label_configure" is not translated in 
pt-rPT, ro, sv
res/values/strings.xml:36: "section_daydream" is not translated in ca, cs, de, 
el-rGR, fr, it, ko, nb, nl, pl, pt-rBR, pt-rPT, ro, ru, sv, uk, zh-rCN, zh-rTW
res/values/strings.xml:50: "send_logs" is not translated in pt-rPT, ro, sv
res/values/strings.xml:51: "send_logs_chooser_title" is not translated in 
pt-rPT, ro, sv
res/values/strings.xml:135: "now" is not translated in cs, de, el-rGR, es, fr, 
it, ko, nl, pl, pt-rBR, pt-rPT, ro, ru, sv, uk, zh-rCN, zh-rTW
res/values/strings.xml:147: "missed_calls_unknown" is not translated in de, 
el-rGR, fr, ko, pl, pt-rPT, ro, sv, zh-rCN, zh-rTW
res/values/strings.xml:159: "sms_body_all_participants_template" is not 
translated in ca, cs, de, el-rGR, es, fi, fr, it, ja, ko, nb, nl, pl, pt-rBR, 
pt-rPT, ro, ru, sk, sv, uk, zh-rCN, zh-rTW

res/values/pref_strings.xml:54: "pref_weather_location_title" is not translated 
in ca, cs, de, el-rGR, es, fi, fr, it, ja, ko, nb, nl, pl, pt-rBR, pt-rPT, ro, 
ru, sk, sv, uk, zh-rCN, zh-rTW
res/values/pref_strings.xml:55: "pref_weather_location_query_hint" is not 
translated in ca, cs, de, el-rGR, es, fi, fr, it, ja, ko, nb, nl, pl, pt-rBR, 
pt-rPT, ro, ru, sk, sv, uk, zh-rCN, zh-rTW
res/values/pref_strings.xml:56: "pref_weather_location_automatic" is not 
translated in ca, cs, de, el-rGR, es, fi, fr, it, ja, ko, nb, nl, pl, pt-rBR, 
pt-rPT, ro, ru, sk, sv, uk, zh-rCN, zh-rTW
res/values/pref_strings.xml:57: "pref_weather_location_automatic_description" 
is not translated in ca, cs, de, el-rGR, es, fi, fr, it, ja, ko, nb, nl, pl, 
pt-rBR, pt-rPT, ro, ru, sk, sv, uk, zh-rCN, zh-rTW
res/values/pref_strings.xml:105: "pref_daydream_color_title" is not translated 
in ca, cs, de, el-rGR, fr, it, ko, nb, nl, pl, pt-rBR, pt-rPT, ro, ru, sv, uk, 
zh-rCN, zh-rTW
res/values/pref_strings.xml:106: "pref_daydream_color_description" is not 
translated in ca, cs, de, el-rGR, es, fi, fr, it, ja, ko, nb, nl, pl, pt-rBR, 
pt-rPT, ro, ru, sv, uk, zh-rCN, zh-rTW
res/values/pref_strings.xml:107: "pref_daydream_night_mode_title" is not 
translated in ca, cs, de, el-rGR, es, fi, fr, it, ja, ko, nb, nl, pl, pt-rBR, 
pt-rPT, ro, ru, sv, uk, zh-rCN, zh-rTW
res/values/pref_strings.xml:108: "pref_daydream_night_mode_description" is not 
translated in ca, cs, de, el-rGR, es, fi, fr, it, ja, ko, nb, nl, pl, pt-rBR, 
pt-rPT, ro, ru, sv, uk, zh-rCN, zh-rTW
res/values/pref_strings.xml:109: "pref_daydream_animation_title" is not 
translated in ca, cs, de, el-rGR, es, fi, fr, it, ja, ko, nb, nl, pl, pt-rBR, 
pt-rPT, ro, ru, sv, uk, zh-rCN, zh-rTW
res/values/pref_strings.xml:110: "pref_daydream_animation_display_names" is not 
translated in ca, cs, de, el-rGR, es, fi, fr, it, ja, ko, nb, nl, pl, pt-rBR, 
pt-rPT, ro, ru, sv, uk, zh-rCN, zh-rTW
res/values/pref_strings.xml:122: "pref_daydream_system_settings_title" is not 
translated in ca, cs, de, el-rGR, fr, it, ko, nb, nl, pl, pt-rBR, pt-rPT, ro, 
ru, sv, uk, zh-rCN, zh-rTW

Original comment by roman.nurik on 17 Jun 2013 at 5:21

[GoogleCodeExporter]

Spanish translations updated. Issue 49

Original comment by david...@gmail.com on 17 Jun 2013 at 11:13

[GoogleCodeExporter]

Can you suggest the tool you are using for translation? Online or offline 
(desktop).

I tried to use some online tools (poeditor.com: not suggested, missed some 
strings; crowdin.net: seems to work ok) but one problem I found is that several 
of these tools destroy the format of the original file, rearrange strings, 
remove comments, etc. This may not be an actual issue, but I would prefer to 
have the translated file in the format of the original one.

Original comment by npla...@gmail.com on 18 Jun 2013 at 9:33

[GoogleCodeExporter]

i'm not sure if this is the correct place to post, so sorry for all the 
notifications. i have my phone in japanese, so today my dashclock lockscreen 
looks like this:

1130
水189月

there should be a 日(day) character between the 18 and the 9 (月 being 
month). how can i make this happen?

Original comment by dgubb...@gmail.com on 18 Sep 2013 at 1:36

[GoogleCodeExporter]

See the Japanese translation thread here:
https://code.google.com/p/dashclock/issues/detail?id=390&can=1&q=Type%3DTracker%
20Component%3DTranslation&colspec=ID%20Type%20Component%20Summary%20Stars%20Stat
us%20TargetRelease

I would, however, think that 9月18日(水) would be the most accurate ordering 
after the addition of the day character. Japan, like Europe, puts the month 
before the Day.

Original comment by Dom...@gmail.com on 18 Sep 2013 at 1:46

[GoogleCodeExporter]

Just a note for #19: AFAIK only the UK uses the MM/DD/YYYY date format in 
Europe. Usually it's DD/MM/YYYY, at the very least in Italy and France.

Original comment by pog...@gmail.com on 18 Sep 2013 at 7:13

[GoogleCodeExporter]

Hi all, I plan on publishing v1.6 in the next two weeks and am not planning on 
making any strings changes. If interested in updating strings for your 
language, please share updated strings in the relevant tracking bug for the 
language. Thanks again!

Original comment by roman.nurik on 10 Dec 2013 at 5:23

[GoogleCodeExporter]

Hi Roman,

I submitted a small patch for a few typos and translation issues in pt-rBR:

https://code.google.com/p/dashclock/issues/detail?id=662

Regards.

Original comment by davidces...@gmail.com on 10 Dec 2013 at 2:33

[GoogleCodeExporter]

Sk updated.
https://code.google.com/p/dashclock/issues/detail?id=196

Original comment by pyler.in...@gmail.com on 10 Dec 2013 at 6:44

[GoogleCodeExporter]

pl olso.
https://code.google.com/p/dashclock/issues/detail?id=148#c20

Original comment by jarko2...@gmail.com on 10 Dec 2013 at 6:57

[GoogleCodeExporter]

I would like also submit the update for Czech Language, but I'm constantly 
receiving "Issue attachment storage quota exceeded." and cannot submit 
attachment :)

Original comment by ales.najmann on 10 Dec 2013 at 7:34

[GoogleCodeExporter]

Hi,

I have created Serbian translation and submitted a pull request (Issue 548).

Original comment by codinglaboratory on 18 Dec 2013 at 5:21

[GoogleCodeExporter]

The Japanese translations submitted on 6/20 by miso should be good to go.  I 
have them another look over and see no issues.  Would be great to finally have 
them implemented.

Original comment by Dom...@gmail.com on 19 Dec 2013 at 2:06

[GoogleCodeExporter]

Yeah, Japanese resources are ready to launch.
http://code.google.com/p/dashclock/issues/detail?id=390

Original comment by miso....@gmail.com on 2 Jan 2014 at 6:22