Ticket #351 (closed enhancement: fixed)
First Polish localization - not complete
| Reported by: | Rudzik | Owned by: | Joel |
|---|---|---|---|
| Priority: | major | Milestone: | Eraser 6.1/6.2 |
| Component: | Internationalisation/Localisation | Version: | |
| Keywords: | Polish translation | Cc: | |
| Processor Architecture: | Blocked By: | ||
| Blocking: | Operating System: |
Description
There are Polish localization:
Eraser\BasePanel.pl.resx Eraser\BlackBoxMainForm.pl.resx Eraser\BlackBoxUploadForm.pl.resx Eraser\LightGroup.pl.resx Eraser\LogForm.pl.resx Eraser\MainForm.pl.resx Eraser\ProgressForm.pl.resx Eraser\Strings.pl.resx Eraser\TaskDataSelectionForm.pl.resx Eraser\TaskPropertiesForm.pl.resx Eraser\UpdateForm.pl.resx Eraser.DefaultPlugins\CustomMethodEditorForm.pl.resx Eraser.DefaultPlugins\CustomMethodPassEditor.pl.resx Eraser.DefaultPlugins\SettingsForm.pl.resx Eraser.DefaultPlugins\Strings.pl.resx Eraser.Manager\Strings.pl.resx ShellExt\ShellExt.rc
ShellExt?.rc is edited by hand, please check its coherence
I could not open SchedulerPanel? and SettingsPanel? in Microsoft Visual C# 2008 Express Edition.
I received these errors:
"SchedulerPanel? --- The base class 'Eraser.BasePanel?' could not be loaded. Ensure the assembly has been referenced and that all projects have been built."
"SettingsPanel? --- The base class 'Eraser.BasePanel?' could not be loaded. Ensure the assembly has been referenced and that all projects have been built."
How to overcome these errors?
Blocking
| Id | Summary | Milestone |
|---|---|---|
| #351 | └ First Polish localization - not complete | Eraser 6.1/6.2 |
Blocked by
| Id | Summary | Milestone |
|---|---|---|
| #351 | └ First Polish localization - not complete | Eraser 6.1/6.2 |
Attachments
Change History
comment:1 follow-up: ↓ 2 Changed 3 years ago by Joel
- Owner set to Joel
- Status changed from new to accepted
comment:2 in reply to: ↑ 1 Changed 3 years ago by Rudzik
Replying to Joel:
You'll need to build the solution first. By the way -- which branch of Eraser did you localise? Trunk or 6.x? I need to know so I know where to apply the patch. There's some voodoo require with csgettext to generate the Polish resx files so perhaps that could be addressed...
Thanks for the patch!
I downloaded eraser6.tar.gz from that link http://eraser.svn.sourceforge.net/viewvc/eraser/trunk/eraser6/ 31st March 2010. I am not sure but it was revision nr 1891.
comment:3 Changed 3 years ago by Joel
Thanks!
Could you please re-upload the attachment, it got lost in translation... (hehe, between old and new servers.)
comment:4 Changed 3 years ago by Rudzik
To build the solution is beyond my skill.
The attachment's md5: d115f3f395733702035c77fe65888034
comment:5 Changed 3 years ago by Joel
Just go to Build > Build solution (Ctrl-Shift-B) but you won't get the Shell extension and Eraser.Util.Native -- you'll also need VC++ Express.
Compiling on VS Express is tedious, I admit.
comment:6 follow-up: ↓ 7 Changed 3 years ago by Joel
I've fixed your RC file, since the rest of the file is in ASCII but your Polish section is in Windows-1250 the Code page pragma must reflect it. Otherwise, the translation looks good! Committed in r1906.
If you want to, you should set up your own local builds of Eraser so you can maintain the localisation, or submit patches from time-to-time, that's fine too.
Would you want to apply the localisation to the current stable 6.0? There may be extra strings to translate.
comment:7 in reply to: ↑ 6 ; follow-up: ↓ 8 Changed 3 years ago by Rudzik
Replying to Joel:
I've fixed your RC file, since the rest of the file is in ASCII but your Polish section is in Windows-1250 the Code page pragma must reflect it. Otherwise, the translation looks good! Committed in r1906.
Thanks!
If you want to, you should set up your own local builds of Eraser so you can maintain the localisation, or submit patches from time-to-time, that's fine too.
Yes, I want to but I have to take some lesson about how-to using Microsoft tools.
Would you want to apply the localisation to the current stable 6.0? There may be extra strings to translate.
Yes sure! Please show me where I find them.
comment:8 in reply to: ↑ 7 Changed 3 years ago by Joel
Replying to Rudzik:
If you want to, you should set up your own local builds of Eraser so you can maintain the localisation, or submit patches from time-to-time, that's fine too.
Yes, I want to but I have to take some lesson about how-to using Microsoft tools.
You can see Compiling Eraser from Source for instructions on how to get the build working.
Would you want to apply the localisation to the current stable 6.0? There may be extra strings to translate.
Yes sure! Please show me where I find them.
You can get them from /branches/eraser6/6.0: http://eraser.svn.sourceforge.net/viewvc/eraser/branches/eraser6/6.0/
comment:9 follow-up: ↓ 10 Changed 3 years ago by Joel
I've added your Polish localisation to the 6.0 branch as well: see r1937. That should simplify your localisation efforts!
comment:10 in reply to: ↑ 9 Changed 3 years ago by Rudzik
Replying to Joel:
I've added your Polish localisation to the 6.0 branch as well: see r1937. That should simplify your localisation efforts!
Thanks! It helped a lot.
I've made update for that strings and for the earlier translation.
6.0.branches 1937 -edited.7z
md5: cceb2b92165c63f6c570b2e998d86b45
eraser6 trunk 1923 -edited.7z
md5: 534ebc2fd927c23b2421bcfc07a78a03
comment:11 Changed 3 years ago by Joel
Applied in r1942-r19343, thanks!
You may like to start translating the UI elements, see Localising Eraser for more information.
comment:12 Changed 3 years ago by Joel
- Status changed from accepted to closed
- Resolution set to fixed
Rudzik, I'll close this ticket first since it's implemented the displayed application strings for both branches. Once you've localised the WinForms?, re-open this ticket and attach the patch.
You'll need to build the solution first. By the way -- which branch of Eraser did you localise? Trunk or 6.x? I need to know so I know where to apply the patch. There's some voodoo require with csgettext to generate the Polish resx files so perhaps that could be addressed...
Thanks for the patch!