Lazarus
Programming => Graphics => Graphics and Multimedia => BGRABitmap and LazPaint => Topic started by: lainz on July 25, 2011, 05:11:51 pm
-
LazPaint support i18n.
We need more translations for LazPaint.
The base lazpaint.po file is here:
https://lazpaint.svn.sourceforge.net/svnroot/lazpaint/lazpaint/release/i18n/lazpaint.po
The base update_checker.po file is here:
https://lazpaint.svn.sourceforge.net/svnroot/lazpaint/lazpaint/update_checker/release/i18n/update_checker.po
How to translate?
Software: I recommend PoEdit http://www.poedit.net/download.php.
This software is recommended too: http://gorm.po.dk/features
Translating: http://wiki.lazarus.freepascal.org/Translations_/_i18n_/_localizations_for_programs#Translating
Post the translations here, I will upload the translations to the LazPaint repository-
https://lazpaint.svn.sourceforge.net/svnroot/lazpaint/lazpaint/release/i18n/
https://lazpaint.svn.sourceforge.net/svnroot/lazpaint/lazpaint/update_checker/release/i18n/
-
You can add czech translation.
But where is program settings dialog? Where interface language can be selected?
-
You can add czech translation.
But where is program settings dialog? Where interface language can be selected?
Thankyou.
Is automatically selected.
-
It is good behaviour to be able to change language. For example if some translation is not good enough and someone prefer english.
What is even more weird is that LazPaint doesn't have preference dialog at all.
It is nice peace of software but so far lack many common features of professional products.
Anyway, thanks for your effort.
-
Thanks for the translation.
In fact, I am proud that there is no preference dialog yet, it means that it is simple to use. :D
But well, yes, why not create such a dialog.
By the way, if you think about a feature that you think may be useful, I invite you to leave a message on LazPaint main thread.
-
Hello, a new version will be published soon. It has some new text tool. There is no translation yet for Spanish and Czech.
-
I've updated spanish translation.
-
Thanx
-
I've done the German translation for the lazpaint.de.po and the update_checker.de.po files.
Both files are in the attachment of this post.
brb
-
I've done the German translation for the lazpaint.de.po and the update_checker.de.po files.
Both files are in the attachment of this post.
brb
Thankyou. added.
-
Translators: there are some new lines of text to translate. Download your respective .po file here:
https://lazpaint.svn.sourceforge.net/svnroot/lazpaint/lazpaint/release/i18n/
-
Hello!
Here it is: German language file of Revision 287
brb
-
Hello!
Here it is: German language file of Revision 287
brb
Nice thanks!
-
Hello people, there is a new version of LazPaint (4.6). I will publish on the Internet soon, so if you have time to translate some new strings...
Needed languages : Deutsch, Español, Czech and Swedish
-
I've commited spanish Translation. Commit nº 300
-
Thanks
-
http://dl.dropbox.com/u/4390580/lazpaint.ja.po
http://dl.dropbox.com/u/4390580/Ss2011-10-03.png
I try to make japanese translation. But It's not work.
Sorry I don't know how to make working correct po file...
Edit: oops, It's my miss...Edit the link.
-
When I go to these addresses I get :
Error (403)
It seems you don't belong here! You should probably try logging in?
-
LazPaint support i18n.
We need more translations for LazPaint.
How to translate?
Software: I recommend PoEdit http://www.poedit.net/download.php.
I've tried poedit and VirTaal on Windows. VirTaal seems much nicer: it looks up the words on the internet (already translated open source projects) and gives you a suggestion you can often just copy over.
Trying VirTaal for a quick & dirty Dutch translation now. I haven't run LazPaint, so I'm just translating the strings...
Edit1: Here
http://www.medionowners.be/index.php?page=tutorials&categorie=2&subcategorie=2&tip=20&titel=Vertaling-van-de-tools-van-photoshop (http://www.medionowners.be/index.php?page=tutorials&categorie=2&subcategorie=2&tip=20&titel=Vertaling-van-de-tools-van-photoshop)
I found a list of English-Dutch translations of terms in the competition's software for reference/comparison ;)
Edit2: I think I found a typo. Shouldn't:
uresourcestrings.rsgradientexpectparameters
Gradient expect 13 parameters :
be
Gradient expects 13 parameters :
Edit3: I don't understand the word "colorness"; it doesn't seem to be an English word - maybe it's something like color intensity, or maybe it's a jargon term that I just don't know about...
Edit4:
uresourcestrings.rsnewexpectparameters
New expect two parameters :
=>
uresourcestrings.rsnewexpectparameters
New expects two parameters :
Same for uresourcestrings.rsopacityexpectparameter, uresourcestrings.rsresampleexpectparameters
-
Dutch translation attached.
-
Thanks BigChimp for your translation and your feedback.
About colorness, well I wanted to express that a pixel can be colored or gray. I don't know if it's real english. :-[
By the way I realised that most translations were wrong. The word before "expects" should not be translated because it is a function name.
-
German translation attached. (Revision 309)
@ Circular:
I'm only one translator.
I neither use LazPaint nor have I downloaded/installed it - in fact have never seen LazPaint - and so I'm only translating the strings to get more "complete" good Lazarus programs. Thus I depend on precise information of the developers. Information, as much as you can give me and the other translators, in the .po-files.
So I think all cited names, function names like the ones in the strings with "expects" should be enclose in quotes,
and
Gradient expects 13 parameters :
should look like
"Gradient" expects 13 parameters :
or
»Gradient« expects 13 parameters :
The last ones are called "french quotes" (if I'm right). Hope they show up correct in my post. Maybe these are applicable for this purpose.
But, I'm only the translator, developers decide.
Bye.
brb
Addition: Yes, they show up correct.
-
'Colorness' I've the same problem trying to translate that.
>>I wanted to express that a pixel can be colored or gray
Color Saturation? Colorfulness?
http://www.ncsu.edu/scivis/lessons/colormodels/color_models2.html#saturation./
-
Thanks BigChimp for your translation and your feedback.
My pleasure, it was nice to get my feet wet with translating while being able to use the work of others :D
Below some more thoughts:
By the way I realised that most translations were wrong. The word before "expects" should not be translated because it is a function name.
Ok, so I think you say the function name itself is not translated. If it is not, how is a non-English user going to found out what the error message actually means? Or is it meant to be kept in English so proper bug reports can be filed?
So I think all cited names, function names like the ones in the strings with "expects" should be enclose in quotes
Depending on the response to my previous point, another option could be to remove the function name from the resource string and append it at runtime using the English function name. This will automatically lead to consistency and cut down on the number of items to be translated.
>>I wanted to express that a pixel can be colored or gray
Color Saturation? Colorfulness?
http://www.ncsu.edu/scivis/lessons/colormodels/color_models2.html#saturation./
Looking at that link, saturation looks like a good word...
-
So I think all cited names, function names like the ones in the strings with "expects" should be enclose in quotes,
and
Gradient expects 13 parameters :
should look like
"Gradient" expects 13 parameters :
or
»Gradient« expects 13 parameters :
The last ones are called "french quotes" (if I'm right). Hope they show up correct in my post. Maybe these are applicable for this purpose.
But, I'm only the translator, developers decide.
Thanks for your translations. :)
That's a good idea to add quotes. By the way, french quotes are inverted and with spaces : « Gradient ».
If it is not, how is a non-English user going to found out what the error message actually means?
If the user has used this function, he should understand it's meaning. This can be explained in documentation, for example here :
http://wiki.lazarus.freepascal.org/LazPaint#General_commands
another option could be to remove the function name from the resource string and append it at runtime using the English function name
Good idea too. In fact we can do both : append at runtime with quotes.
Looking at that link, saturation looks like a good word...
Yes, it means saturation, but I don't like this word. I find that colorness is more intuitive. But well, if it's not easy to understand, I will put the standard word instead.
EDIT : changes applied on subversion.
-
Updated Dutch main translation for r310
-
I've added japanese, updated dutch and spanish.
-
Thanks.
Daniel sent me an update for swedish translation.
-
Language is not fully reflected in the menus
+
I have a problem
lazpaint.lpr(45,18) Error: Identifier not found "LRSTranslator"
This is V 4.6
linux gtk 686
fpc version 2.4.2-0
lazarus 0.9.30
I hope add the language
-
Add LResources to the uses clause.
Thanks for the translation.
-
Add LResources to the uses clause.
Thank you .. is worked
Correct translation in Attachments
I need a global variable "FallbackLang"
LCLGetLanguageIDs(Lang,FallbackLang);
To change the direction of the window..
If FallbackLang ="ar" then
self.BiDiMode:=bdRightToLeft;
I put code in each self.show ,or there is another way...?
-
I don't know.
Hmm... your translation does not seem to be using last svn. Here is the current version :
-
I added translations for dialogs (LCLStrConsts)
-
Submitted new Dutch translation for LCLStrConts to Lazarus bugtracker:
http://bugs.freepascal.org/view.php?id=20439 (http://bugs.freepascal.org/view.php?id=20439)
Seems the version in Lazarus SVN & yours is not the same; my patch applied only partially.
Still, some translations were updated - attached your version, patched.
-
Add LResources to the uses clause.
Thank you .. is worked
Correct translation in Attachments
I need a global variable "FallbackLang"
LCLGetLanguageIDs(Lang,FallbackLang);
To change the direction of the window..
If FallbackLang ="ar" then
self.BiDiMode:=bdRightToLeft;
I put code in each self.show ,or there is another way...?
I suggest to add to the resourcestring a "translation" that called Bidi or something like that, and when it is true on the po (mo actually) file the direction should be set to right to left.
-
Submitted new Dutch translation for LCLStrConts to Lazarus bugtracker:
http://bugs.freepascal.org/view.php?id=20439 (http://bugs.freepascal.org/view.php?id=20439)
Seems the version in Lazarus SVN & yours is not the same; my patch applied only partially.
Still, some translations were updated - attached your version, patched.
Thanks.
-
Hello, I received this e-mail from download3k :
We just launched the French, Spanish and Russian versions of our site, with German and Romanian soon to come.
If you wish to have your program listed there as well, simply update your pad file with French, German, Spanish, Russian or Romanian descriptions.
Can I have some help with these translations ?
The existing pad file contains this :
<French>
<Keywords>éditeur graphique image filtres antialiasing transparence</Keywords>
<Char_Desc_45>LazPaint est un éditeur d'images</Char_Desc_45>
<Char_Desc_80>LazPaint est un éditeur d'images avec de nombreux outils et filtres</Char_Desc_80>
<Char_Desc_250>LazPaint est un éditeur d'images avec de nombreux outils et filtres, écrit en Lazarus (Free Pascal). Le tracé est réalisé avec antialiasing, y compris pour la sélection. Les couleurs peuvent être ajustées</Char_Desc_250>
<Char_Desc_450>LazPaint est un éditeur d'images avec de nombreux outils et filtres, écrit en Lazarus (Free Pascal). Le tracé est réalisé avec antialiasing, y compris pour la sélection. Les couleurs peuvent être ajustées et le logiciel peut lire les fichiers de Paint.NET. Fonctions clés : génération de textures, formes éclairées, ajustement des couleurs, filtres, déformations</Char_Desc_450>
<Char_Desc_2000 />
</French>
<English>
<Keywords>editor graphic image filters antialiasing alphablending transparency</Keywords>
<Char_Desc_45>LazPaint is a graphic editor</Char_Desc_45>
<Char_Desc_80>LazPaint is a graphic editor with many tools and filters</Char_Desc_80>
<Char_Desc_250>LazPaint is a graphic editor with many tools and filters, written in Lazarus (Free Pascal). The drawing is done with antialiasing, including selection. Colors can be adjusted.</Char_Desc_250>
<Char_Desc_450>LazPaint is a graphic editor with many tools and filters, written in Lazarus (Free Pascal). The drawing is done with antialiasing, including selection. Colors can be adjusted and the program can read Paint.NET files. Key features : texture generation, shaded shapes, color adjustment, filters, deformations</Char_Desc_450>
<Char_Desc_2000 />
</English>
<Spanish>
<Keywords>imagen editor visor filtros color pintar zoom</Keywords>
<Char_Desc_45>LazPaint es un editor de imágenes.</Char_Desc_45>
<Char_Desc_80>LazPaint es un editor de imágenes, como PaintBrush o Paint.NET.</Char_Desc_80>
<Char_Desc_250>LazPaint es un editor de imágenes, como PaintBrush o Paint.NET, creado en Lazarus (Free Pascal). Usa la librería BGRABitmap para dibujar.</Char_Desc_250>
<Char_Desc_450>LazPaint es un editor de imágenes, como PaintBrush o Paint.NET, creado en Lazarus (Free Pascal). Usa la librería BGRABitmap para abrir/guardar BMP, PNG, JPG y abrir PDN, GIF & ICO. Tiene la función Smart zoom x3. Manipulación de color: Colorize, Shift colors, Intensity, Lightness, Normalize, Negative, Linear negative & Grayscale. Filtros: Radial blur, Motion blur, Custom blur, Sharpen, Smooth, Median, Contour, Emboss, Sphere, Cylinder & Clouds.</Char_Desc_450>
<Char_Desc_2000 />
</Spanish>
If you are lost with XML, you can use PadGen.
http://www.download3k.com/languages-guide.php
@lainz: can you update the spanish version ?
-
Ok i'm posting here the translation:
<Spanish>
<Keywords>editor graficos imagen filtros antiafilado alphablending transparencia</Keywords>
<Char_Desc_45>LazPaint es un editor de gráficos</Char_Desc_45>
<Char_Desc_80>LazPaint es un editor de gráficos con varias herramientas y filtros</Char_Desc_80>
<Char_Desc_250>LazPaint es un editor de gráficos con varias herramientas y filtros, escrito en Lazarus (Free Pascal). El dibujo es realizado con antiafilado, incluyendo la selección. Los colores se pueden ajustar.</Char_Desc_250>
<Char_Desc_450>LazPaint es un editor de gráficos con varias herramientas y filtros, escrito en Lazarus (Free Pascal). El dibujo es realizado con antiafilado, incluyendo la selección. Los colores se pueden ajustar y el programa puede leer archivos de Paint.NET. Funciones destacadas : generación de texturas, formas sombreadas, ajuste de color, filtros y deformaciones.</Char_Desc_450>
<Char_Desc_2000 />
</Spanish>
-
Thanks.
-
If you need a german Translation for the padfile;
<German>
<Keywords>Editor Grafik Bild Filter Antialiasing Alphablending Transparenz</Keywords>
<Char_Desc_45>LazPaint ist ein Grafikeditor</Char_Desc_45>
<Char_Desc_80>LazPaint ist ein Grafikeditor mit vielen Funktionen und Filtern</Char_Desc_80>
<Char_Desc_250>LazPaint ist ein Grafikeditor mit vielen Funktionen und Filtern, geschrieben in Lazarus (Free Pascal). Die Darstellung erfolgt mit Antialiasing, inklusive Auswahlmöglichkeit. Farben können angepasst werden.</Char_Desc_250>
<Char_Desc_450>LazPaint ist ein Grafikeditor mit vielen Funktionen und Filtern, geschrieben in Lazarus (Free Pascal). Die Darstellung erfolgt mit Antialiasing, inklusive Auswahlmöglichkeit. Farben können angepasst werden. Das Programm kann Paint.NET- Dateien lesen. Wichtige Merkmale : Generierung von Texturen, schattierte Formen, Farbanpassung, Filter, Verformungen</Char_Desc_450>
<Char_Desc_2000 />
</German>
-
Thanks !
-
Hello, LazPaint would need some translations for version 4.8. If you have time to do it, please post your translation here.
Already done : English, French
-
Spanish ready,.
-
Thanks.
-
Dutch version based on Revision 431
Don't know if you need an entry in the pad file:
<Dutch>
<Keywords>editor graphics beeld filters antialiasing alphablending transparantie</Keywords>
<Char_Desc_45>LazPaint is een graphics editor</Char_Desc_45>
<Char_Desc_80>LazPaint is een graphics editor met vele tools en filters</Char_Desc_80>
<Char_Desc_250>LazPaint is een graphics editor met vele tools en filters, geschreven in Lazarus (Free Pascal). Er wordt getekend met antialiasing, inclusief selectie. Kleuren kunnen aangepast worden.</Char_Desc_250>
<Char_Desc_450>LazPaint is een graphics editor met vele tools en filters, geschreven in Lazarus (Free Pascal). Er wordt getekend met antialiasing, inclusief selectie. Kleuren kunnen aangepast worden en het programma kan Paint.NET bestanden lezen. Hoofdfuncties: texturegeneratie, vormen met schaduwen, kleuraanpassing, filters, vervormingen.</Char_Desc_450>
<Char_Desc_2000 />
</Dutch>
-
Thanks :)
-
If you can make some translations for LazPaint, please tell me so that I do not publish version 5.1 immediately.
Translations updates to do : arabic, czech, german, japanese, russian, swedish
Minor translation update to do : spanish (already done up to version 5.0)
Languages already done : english, french, dutsch
Latest translations are here :
http://sourceforge.net/p/lazpaint/code/505/tree/lazpaint/release/i18n/
To know if some translation are not done or unchecked, find << msgstr "" >> and << fuzzy >>
-
Working on nl/Dutch.
What does
Zoom layer stack in
mean? Zooming into a "stack of layers", i.e. going to a deeper layer? Or something else
-
in lclstrconsts.po
No HTML Browser found.%sPlease define one in Environment -> Options -> Help -> Help Options
edit:
... needs a space before/after the %s (and what is inserted anyway? The browser name?)
Just had a look at the Lazarus source lazhelphtml.pas:
ErrMsg:=Format(hhsHelpNoHTMLBrowserFoundPleaseDefineOne,[LineEnding])
so it inserts #13#10 (or #10 if you're a penguin), so that's fine.
... and this is just awful - a huge complicated sentence:
--sync Call XSynchronize (display, True) after the Xserver connection has been established. This makes debugging X protocol errors easier, because X request buffering will be disabled and X errors will be received immediately after the protocol request that generated the error has been processed by the X server.
... but I guess it's an LCL message, so not really a lazpaint problem...
-
Ok, done with the translation unless the answer to my question above is different - then I'll upload a new version.
(Love Virtaal - lets you look up words etc, very handy)
-Edit: removed obsolete translation. see post below
-
Working on nl/Dutch.
What does
Zoom layer stack in
mean? Zooming into a "stack of layers", i.e. going to a deeper layer? Or something else
The stack of layer is a window that shows all the layers. This view can be zoomed in or out.
-
Ok, so a layer overview window. I'll change the translation.
-
Updated
-
Thank you very much :)
-
My pleasure - hope we don't get too many users complaining about the translation ;)
-
Well never had any complaint about translations, so I think we're safe.
Anyway, never had any donation either, so...
-
It think that translations files got mixed up, because I don't understand that LazPaint translations arrived in lclstrconsts files.
-
Wow that's crazy ::)
BTW you can improve the translation files removing the duplicates. This can be done disabling 'Auto update .po file when saving form' (something like that, a checkbox in the internationalization tab in project options).
Then put all in resource strings and put a translation code OnCreate or in a procedure that you can handle. Like Caption := rsCaptionForm1; btn1.Caption := rsBtn1Caption; label1.Caption := rsLabel1Caption; etc..
And bye bye duplicated strings! Of course it's 'harder' but is better.
-
You're right Lainz, but I do not feel courageous enough.
Well, at least, I reverted the bug so that now lclstrconsts are not crazy anymore.
-
Arabic translation update + Correct mistakes :-\
-
Thank you, i've added it.
There are still some translations left. See the new file in the online folder.
http://sourceforge.net/p/lazpaint/code/571/tree/lazpaint/release/i18n/
Files to be translated :
lazpaint.ar.po
lazpaint.cs.po
lazpaint.ja.po
lazpaint.ru.po
lazpaint.sv.po
-
lazpaint.es.po done.
I need to tell google translator some things.. luckily there dictionaries
Attached the translation, I need to trim the translation or you can use some align to fix this (see image attached).
-
Just some nagging, hope you don't mind ;)
What does
Merge layer over
mean exactly?
1. Merge a certain layer over... what?
2. Put the layer over the existing layers?
3. Combine the layer with existing layers?
I'm assuming it's 3.
Also, why do we get this:
tfmain.layerrotate.caption
LayerRotate
Is "LayerRotate" really a caption? Or should it be something like "Rotate layer"?
similar question for tfmain.tool_textaligncenter.caption/Tool_TextAlignCenter
similar question for tfmain.tool_textalignleft.caption/Tool_TextAlignLeft
etc
tfmain.toolgradient.caption
Gradient (G')
Wouldn't it be better to just put Gradient (%s') and fill out the shortcut key (assuming G is the shortcut key) programmatically? Would make translation easier and also make it easier to create a custom keybinding scheme ;)
Anyway, here's the Dutch translation...
-
Merger layer over means merge layer over the one that is just underneath
Wouldn't it be better to just put Gradient (%s') and fill out the shortcut key (assuming G is the shortcut key) programmatically? Would make translation easier and also make it easier to create a custom keybinding scheme ;)
You're absolutely right. I will think about it for next version.
Anyway, here's the Dutch translation...
Thanks.
-
Also, why do we get this:
tfmain.layerrotate.caption
LayerRotate
Is "LayerRotate" really a caption? Or should it be something like "Rotate layer"?
similar question for tfmain.tool_textaligncenter.caption/Tool_TextAlignCenter
similar question for tfmain.tool_textalignleft.caption/Tool_TextAlignLeft
etc
You don't need to translate them, these are not shown, even if they are called 'caption'.
That's wonderful, I have a dutch version of LazPaint. :)
-
You don't need to translate them, these are not shown, even if they are called 'caption'.
That's wonderful, I have a dutch version of LazPaint. :)
Well, don't put them into the .po file then ;)
Just kidding.... it's just a couple of lines anyway.
Glad I could help with the translation.
-
Well, don't put them into the .po file then ;)
Maybe you don't know that po files are generated automatically. Or maybe you're making fun of me.
-
I'm definitely not making fun of you - I'm sorry if that was your impression.
I've used .po files once or twice but you're right, I didn't know/remember it autogenerates the text for captions...
I suppose in theory the .po generation could check for captions that are invisible/don't show but then the entire source .pas would need to be scanned as well to see if .visible ever changes...
-
With patience we can remove the duplicates and remove the autogenerated things. I can try to do that, but It will take time.
-
Ok, no hurry :) Translating some extra strings is not a problem... it's easy enough to do in a couple of minutes...
Thanks!
-
Well, it's not so important. I guess I can put empty strings in those captions or the same thing as in the hints, so it will just be duplicates. Most duplicates occur because there is a caption and a hint that contains the same thing.
-
Ok.
PD: trying shadow text from the post editor =) Nicee!
-
Ok.
PD: trying shadow text from the post editor =) Nicee!
Oh that's fun !
-
Alright, I found how to remove some of the unused translations, and others have become duplicates.
-
Hello! I'm working on the german translation. Using r571.
1)What is a "Spec. index :"
a) Spectral index
b) Specified index
c) Something else ???
2) There is a dot (period, point, .) in line 66. Does it need to be translated?
3) I'm working on "Rendering" (Line 1947). Is it
a) a menu item?
b) a heading for a choice of several Rendering methods?
c) a hint like: I'm rendering now!
4) There are some translations marked as fuzzy. Seems some of them have changed their meaning. I tried to correct them.
Some others appear to be correct. What now? Should I remove the fuzzy marker or leave it as is?
Please consider that I might not be a totally stupid moron. I had only a quick glance at LazPaint and this was long time ago. Thank you!
Billy Ray Bones
-
Hello! I'm working on the german translation. Using r571.
Hello billyraybones. Thanks for taking some time.
1)What is a "Spec. index :"
a) Spectral index
b) Specified index
c) Something else ???
It means "specular index", it is "how much the light is concentrated"
2) There is a dot (period, point, .) in line 66. Does it need to be translated?
You can ignore it.
3) I'm working on "Rendering" (Line 1947). Is it
a) a menu item?
b) a heading for a choice of several Rendering methods?
c) a hint like: I'm rendering now!
It is the title of the Rendering tab.
4) There are some translations marked as fuzzy. Seems some of them have changed their meaning. I tried to correct them.
Some others appear to be correct. What now? Should I remove the fuzzy marker or leave it as is?
If the translation matches, you can remove the fuzzy marker. It is just a hint to look at it because it may not match anymore.
Please consider that I might not be a totally stupid moron. I had only a quick glance at LazPaint and this was long time ago. Thank you!
Billy Ray Bones
Your help is appreciated as my german sucks. :)
-
Hello again from the german translator!
I included the fixes for the discussed issues and had a close look on the whole translation file. Some minor errors had to be fixed as well. So now here is the result of the ...
Billy Ray Bones
-
Thanks !
-
As it is difficult to have translations that are up-to-date, I've added an online update of languages files inside LazPaint. So you can send me your translations whenever you have the time to do them, and theoretically, they will be available for users !
Here are latest language files :
https://sourceforge.net/p/lazpaint/code/603/tree/lazpaint/release/i18n/
If you don't know, what is needed is to put something between double quotes on the lines which begin with msgstr, according to what is written in english on the previous line which begins with msgid.
Do not translate equalities like "Blue =" because in this case blue is the name of the variable for the blue component.
Strings left to be translated
lazpaint.ar.po : 75
lazpaint.cs.po : 157
lazpaint.de.po : 0
lazpaint.es.po : 14
lazpaint.fr.po : 0
lazpaint.ja.po : 111
lazpaint.nl.po : 0
lazpaint.po : 458
lazpaint.ru.po : 77
lazpaint.sv.po : 107
-
Hello circular,
1) Some strings (HSL, RGB) should not appear in the .po files, as these are abbreviations that stand for color models which are known all over the world as such. [Likewise NASA (the American space guys) or BBC (the British TV company) should not be translated either]
2) Questionable:
Blue =
Green =
Red =
and the B, G, R ? (No problem in German, as Blue=Blau, Green=Grün, Red=Rot) But should we do this? I'm hoping to hear the opinion from other translators, too!
Again: B, G and R refer to the RGB color model.
And more:
Hue =
Saturation =
Lightness =
refer to the HSL model. (But could/should/need these to be translated? I've no idea 'bout this.)
3) One easy one: Does "Shaded map" mean "Grayscale"?
BTW: I translated all but the above!
Billy Ray Bones
-
Yes, Hue/Saturation/Lightness should be translated IMO. E.g. saturation would be verzadiging in Dutch and probably something similar in German. AFAIU, verzadiging is the proper term even though many people over here probably use the English term.
I think I posted an English=>Dutch translation overview of Photoshop terms earlier in this thread - this'll show if a term is actually translated. Additionally, I use Virtaal which can look up existing translations in open source programs (like Gnome/KDE and their tools). Very useful to find out technical terms.
-
Yes and no. These strings in particular should not be translated because there are variables in maths expressions, they must remain plain ASCII. RGB and HSL model names could be translated, but that would be maybe confusing if the variable names are not translated too.
3) One easy one: Does "Shaded map" mean "Grayscale"?
No, shaded map means that it is an alititude map which has lighter and darker parts according to the phong lighting model.
I've merged your translation with someonelse's translation to german. Can you have a look at the resulting file?
-
I had a look at your file - looks good. Only 3 or 4 minor corrections (typo, capitalization).
These strings in particular should not be translated because there are variables in maths expressions, they must remain plain ASCII.
Remove these from the po files.
RGB and HSL model names could be translated, but that would be maybe confusing if the variable names are not translated too.
I think we'll leave them just as they are now in your file.
Same goes for "Shaded map" -leave it as well, for now.
@ BigChimp:
I took a look for the appropriate terms at Photoshop Elements by myself. Thanks for the hint on Virtaal. I will try it in the near future.
Bye
Billy Ray Bones
Seems there are problems with saving my zip attachment. Will try again later.
-
Yes, at least from yesterday I can't attach. ::)
-
These strings in particular should not be translated because there are variables in maths expressions, they must remain plain ASCII.
Remove these from the po files.
That's not so easy, because po files I generated automatically.
Same goes for "Shaded map" -leave it as well, for now.
German people speak English ?
-
Updated Dutch translation:
https://bitbucket.org/reiniero/fpc_laz_patch_playground/downloads/lazpaint.nl.po
(cannot attach, so uploaded there)
Not going into the German people speaking English debate... afraid to get a "do Dutch people speak German" reply ;)
-
German people speak English ?
Some do!
Well alright, I'll think about it.
BRB
No attachments today.
-
Try to use constant strings instead resource strings, and in Labels / Forms use empty captions '' or 'notranslate' and fill them on runtime.
-
Updated Dutch translation:
https://bitbucket.org/reiniero/fpc_laz_patch_playground/downloads/lazpaint.nl.po
Thanks.
Not going into the German people speaking English debate... afraid to get a "do Dutch people speak German" reply ;)
Oh come on, I know you all speak English very well!
That's a real question. Sometimes, when listening to german radios, I get the feeling that they speak a mixture of german and english.
-
Try to use constant strings instead resource strings, and in Labels / Forms use empty captions '' or 'notranslate' and fill them on runtime.
That's interesting. Where is this notranslate option?
-
Try to use constant strings instead resource strings, and in Labels / Forms use empty captions '' or 'notranslate' and fill them on runtime.
That's interesting. Where is this notranslate option?
There's no option :)
I say:
const
rsLabel1 = 'Label1'; >> this is not added in the .po file
resourcestring
rsLabel1 = 'Label1';
Form.Label1.Caption = 'notranslate' or '' (empty) >> this in the IDE, Object Inspector.
So when you create the form add:
Form.Label1.Caption := rsLabel1;
And it will be not translated.
In the .po file Form.Label1.Caption will say 'notranslate' so you can advise the translators that doesn't need to translate that things.
Also if they translate those will not be used because you will assign a constant string OnCreate.
-
I understand. It's just that I don't like the idea that the interface is not readable in design mode.
-
Dutsch translation is online, so that LazPaint 5.6 will automatically download it.
Here is the update list for po files to be translated :
lazpaint.ar.po : 75
lazpaint.cs.po : 157
lazpaint.de.po : 0 (waiting to be validated or corrected by billyraybones)
lazpaint.es.po : 14
lazpaint.ja.po : 111
lazpaint.po : 458
lazpaint.ru.po : 77
lazpaint.sv.po : 107
@billyraybones:
If there are a few changes, you can explain it here, instead of sending the entire file.
-
Ok.
Just add the constant strings and you're done.
The translators will translate that automatically generated strings but it will don't affect LazPaint.
-
Attached translation.
Hey you readed my mind! I was thinking on 'Shaded map' some days ago to add to the 'NoiseBWA' filter in BCFilters to create a metallic thing!!
Attached a picture.
Is basically:
- BCFilters.NoiseBWA
- LazPaint.Shaded map
- LazPaint.set background remove alpha
- Smooth
Attached.. well download, because the Attachments does not works for me.
Download translation: https://dl.dropbox.com/u/2434440/lazpaint.es.7z
Picture: http://www.subirimagenes.com/imagen-metalic-8360909.html
-
Thanks for your translation. It's online too.
Hey you readed my mind! I was thinking on 'Shaded map' some days ago to add to the 'NoiseBWA' filter in BCFilters to create a metallic thing!!
I don't really understand. We thought of the same thing?
Is basically:
- BCFilters.NoiseBWA
- LazPaint.Shaded map
- LazPaint.set background remove alpha
- Smooth
Good idea.
Maybe you can add blur and normalize after noise, in order to choose the size of the grain.
You may generate noise in LazPaint using apply function with random value.
-
Thanks for your translation. It's online too.
Hey you readed my mind! I was thinking on 'Shaded map' some days ago to add to the 'NoiseBWA' filter in BCFilters to create a metallic thing!!
I don't really understand. We thought of the same thing?
Is basically:
- BCFilters.NoiseBWA
- LazPaint.Shaded map
- LazPaint.set background remove alpha
- Smooth
Good idea.
Maybe you can add blur and normalize after noise, in order to choose the size of the grain.
You may generate noise in LazPaint using apply function with random value.
I don't know, at least I think on the resulting image some days ago, and your filter fits exactly.
I thought on using something like phong shading to create the image, but not tried nothing.
I'll try the apply function.
-
Oh ok, I understand.
About translations, I'm sorry if I made some people uncomfortable. That's not my intention.
I'm just reminding you people of the cruel reality, that users of LazPaint may not understand english, and that in order to make it simple, there can be only one update for each language after the software is released, so that I'd rather put translation files that are the most translated possible.
Of course, that's not mandatory, if you say that you just don't find how to translate it, or that you are not motivated to find all translations, that's ok.
Some translations may sound ridiculous in the first place, because we always heard it in english, but translating it anyway preserves your language, which is good thing, right?
It does not need to be that exact same words, but to express the idea.
-
Of course, I've no problem the new translations does not contain a lot of text, so updating is easy, at least for me that I've already translated something :) Maybe it's harder to start a new translation..
-
I'm just reminding you people of the cruel reality, that users of LazPaint may not understand english, and that in order to make it simple, there can be only one update for each language after the software is released, so that I'd rather put translation files that are the most translated possible.
Of course, that's not mandatory, if you say that you just don't find how to translate it, or that you are not motivated to find all translations, that's ok.
Some translations may sound ridiculous in the first place, because we always heard it in english, but translating it anyway preserves your language, which is good thing, right?
It does not need to be that exact same words, but to express the idea.
Well... I partly agree ;) A lot of English IT terms are e.g. used when speaking Dutch, sometimes with Dutch alternatives, sometimes not.
Using industry-standard terms helps IMO; inventing your own terms requires the users to mentally translate the concepts... even if it the Lazpaint concept is a nice word in their own language.
An example in English that I have my doubts on (but note I'm a graphics newbie, so I may be completely wrong):
altitude map=> could this be height map https://en.wikipedia.org/wiki/Heightmap
I also think the translator should be the one who gets to decide what is the suitable word to use rather than the program author if he's not a native speaker... (given that the translator really understands what concepts are meant, which in e.g. my case is not so)
Anyway, I don't want to look for a fight or something, I'm happy enough translating Lazpaint and just wanted to voice my opinion;)
-
We're not in a software company.
Using industry-standard terms helps IMO;
It's not an issue of industry-standard terms, but of translation. Hence the question about using untranslated terms. If you tell me that in your langage, this term is never translated, then ok, it's validated. If you tell me that you don't know so you will just let the term untranslated, well, that's not what I would consider as validated.
inventing your own terms requires the users to mentally translate the concepts... even if it the Lazpaint concept is a nice word in their own language.
This is a miror effect. Lazpaint is a proper noun, so it's not a valid example. Same thing for example apply to ClearType.
An example in English that I have my doubts on (but note I'm a graphics newbie, so I may be completely wrong):
altitude map=> could this be height map https://en.wikipedia.org/wiki/Heightmap
In fact, you're trying to argue that you're right by demonstrating that I'm wrong. And it doesn't prove your point at all, because for example the german version of it is Höhenfeld, which is translated.
In fact, it's not an error, I did it on purpose, to avoid the confusion with the height of the bitmap.
I also think the translator should be the one who gets to decide what is the suitable word to use rather than the program author if he's not a native speaker...
That's why I don't do the translations myself. And also because it takes some time. I published your translation with "shaded map" not translated because you are the authority regarding dutsch translation. Yes, you are responsible for it because nobody else is, just like I am responsible for LazPaint because nobody else is. You can put anything you want in the translation, which does not mean that you must write nonsense!
For german translation, it's a bit more complicated, because there are in fact three people involved. Another translator told me that the word "Licht" should be changed to "Helligkeit" but at the same time, there is not much room for the word. Finally I added some code so that if the translation is too long, the text is rearranged to fit, and at the same time, the word "Licht" is used anyway.
If we want to have the best german translation possible, let's be consistent and try to translate "Shaded map" too. But of course, this effort is not mandatory, we are free not to translate something, we're not paid for it, and users can look on the internet for the meaning of the words if they don't understand it.
(given that the translator really understands what concepts are meant, which in e.g. my case is not so)
Anyway, I don't want to look for a fight or something, I'm happy enough translating Lazpaint and just wanted to voice my opinion;)
I'm not interested in fighting either.
I conclude that your reaction comes from the fact that you are uncertain about the meaning of the terms.
-
Using industry-standard terms helps IMO; inventing your own terms requires the users to mentally translate the concepts... even if it the Lazpaint concept is a nice word in their own language.
Lazpaint is a proper noun, so it's not a valid example. Same thing for example apply to ClearType.
Sorry, I was unclear, I didn't mean the word "Lazpaint" itself, but the word Lazpaint uses to denote an object/idea/concept. (E.g. altitude map)
In fact, you're trying to argue that you're right by demonstrating that I'm wrong. And it doesn't prove your point at all, because for example the german version of it is Höhenfeld, which is translated.
I think you misunderstood what I was trying to say: my point was it's better to use well known terms for concepts. I wasn't specifically talking about translations, I was talking about using industry terms. I picked an English example because a Dutch example may not be so well understood ;)
In fact, it's not an error, I did it on purpose, to avoid the confusion with the height of the bitmap.
As I said, I'm not an expert, and haven't run LazPaint more than a couple of minutes, so that may be a very valid reason.
I also think the translator should be the one who gets to decide what is the suitable word to use rather than the program author if he's not a native speaker...
That's why I don't do the translations myself. And also because it takes some time. I published your translation with "shaded map" not translated because you are the authority regarding dutsch translation. Yes, you are responsible for it because nobody else is, just like I am responsible for LazPaint because nobody else is.
I like somebody who clearly defines responsibilities... especially if they match my own viewpoints...
For german translation, it's a bit more complicated, because there are in fact three people involved. Another translator told me that the word "Licht" should be changed to "Helligkeit" but at the same time, there is not much room for the word. Finally I added some code so that if the translation is too long, the text is rearranged to fit.
And AFAIK "Helligkeit" translates back to "brightness"... but that's a bit beside the point.
If we want to have the best german translation possible, let's be consistent and try to translate "Shaded map" too.
As the Germans translate a lot (much more than the Dutch) it is very likely there is an industry standard German term for "shaded map", so yes, I would agree.
But of course, this effort is not mandatory, we are free not to translate something, we're not paid for it, and users can look on the internet for the meaning of the words if they don't understand it.
Yep. I wish we would get some actual users telling us how they feel about the translation!
I'm not interested in fighting either.
Good - no offense meant and none taken.
I conclude that your reaction comes from the fact that you are uncertain about the meaning of the terms.
I don't really think so. As I said, I looked up industry terms in the competition's product and I asked earlier in this thread when I didn't understand something.
The point I was trying to make is that:
1. In general: it's better to use industry standard terms than new terms (specific to Lazpaint only). Of course, you're responsible for the program and terminology, I can only suggest
2. In translation: sometimes these industry standard terms are the English terms, e.g. in Dutch: not translating "Phong shading"... haven't looked if I actually followed that, so no flames please ;)
Hope this clears up what I tried to say. If not... I think we agree on the important points anyway ;)
-
Alright.
I think you misunderstood what I was trying to say: my point was it's better to use well known terms for concepts. I wasn't specifically talking about translations, I was talking about using industry terms. I picked an English example because a Dutch example may not be so well understood ;)
Alright.
In fact, it's not an error, I did it on purpose, to avoid the confusion with the height of the bitmap.
As I said, I'm not an expert, and haven't run LazPaint more than a couple of minutes, so that may be a very valid reason.
I don't know, but it's just that I don't like these kind of confusion. I suppose it comes from my mathematical background.
I like somebody who clearly defines responsibilities... especially if they match my own viewpoints...
lol
Well, it's not obvious with opensource software when there is no official leading. Maybe it's a weekness. At the same time, we are all free to participate if we want, so I don't find any legitimacy in defining those responsabilities. So they come up with the presence of people and their involvement.
For german translation, it's a bit more complicated, because there are in fact three people involved. Another translator told me that the word "Licht" should be changed to "Helligkeit" but at the same time, there is not much room for the word. Finally I added some code so that if the translation is too long, the text is rearranged to fit.
And AFAIK "Helligkeit" translates back to "brightness"... but that's a bit beside the point.
It's to illustrate that I have to manage three translators (including me because I speak a little bit german), and that translation issues involves some coding for me. So I understand that translators may not want to spend time in translations, but I may not want to spend time in coding either.
As the Germans translate a lot (much more than the Dutch) it is very likely there is an industry standard German term for "shaded map", so yes, I would agree.
There is "Phong-Beleuchtungsmodell" and "Höhenfeld" in wikipedia.
Yep. I wish we would get some actual users telling us how they feel about the translation!
Yes. There is not much feedback. At the same time, feedback means that we read it and take it into account, so it means having spare time.
1. In general: it's better to use industry standard terms than new terms (specific to Lazpaint only). Of course, you're responsible for the program and terminology, I can only suggest
I agree with that, except to the extent that if I prefer some word for some reason, I will happily tread on industry standard terms. In fact, you're not only suggesting, because you can apply this view to your translation anyway.
2. In translation: sometimes these industry standard terms are the English terms, e.g. in Dutch: not translating "Phong shading"... haven't looked if I actually followed that, so no flames please ;)
Oh afraid of inferno. Don't be, as far as I am concerned, it does not exist.
Hope this clears up what I tried to say. If not... I think we agree on the important points anyway ;)
Yes, this was useful to take about that.
-
All good then...
I opened another thread to ask for feedback on translations.
Yes, implementing suggestions etc will take time - at the same time, as you said, we're all volunteers, so we're the ones that decide when we'll spend time on it...
-
Yep.
-
So, how do we translate shaded map? Beleuchtet Höhenfeld? Beleuchtetes Höhenfeld?
-
Just put one and get the feedback, if there's one.
Maybe LazPaint need their own website, or at least a forum (maybe sourceforge has some forum that you can add to your current website in sourceforge - I say something like the 7zip forum), a feedback button in LazPaint that points to some feedback page. No one 'end user' will come to a programming site (I've seen only one or two in all LazPaint time..).
I've never received feedback about my translation :) Also my e-mail is not in the translated file (please don't add it :) (well, I can decide it of course), it's better for me but not for the feedback) also there's nothing in the about dialog (some programs put the info to contact the translator by email or translator website - and mostly they're broken :-[ by time passing).
BTW mantain a forum is an incredible experience both as tedious. I held forums from more than six years, and there comes a time when it is best to give it to someone else :)
that's the best to add it on sourceforge, not so easy to give it away (?)
-
PD: translations are a problematic thing, I don't know why, one of the projects I've contributed with some translations DeSmuME (desmume.org, or find it on sourceforge) currently removed translations (7 or more languages available).
They was using a bad system, translating directly from resources (something like copy and paste the .lfm and translate, but in Visual Studio). << That's terrible.
The advantage is that LazPaint uses .po, so the program will always look 'complete' also if translations are not finished.
-
Yeah, thanks to Lazarus including i18n :)
-
Check this:
http://www.po-auto-translator.tk/
-
It needs Java. I don't have it installed because I have problems using it (with update system and with web browser integration)
-
Ok, basically it automatically translates a po file from any language to any language.
Of course is not perfect, but can helps people don't understand english to begin a translation.
-
I understand
-
Updated Czech translation file.
-
Thanks. Czech translation is online. :)
-
Deutsch translation is online. :)
-
Here are translations left to be done :
lazpaint.ar.po : 75
lazpaint.ja.po : 111
lazpaint.ru.po : 77
lazpaint.sv.po : 107
http://sourceforge.net/p/lazpaint/code/616/tree/lazpaint/release/i18n/
-
circular..
Here is the Arabic translation
-
Hi,
I'm the author of this topic, now my nick is 007 and I've updated the spanish translation for the latest svn (attached).
-
Updated Dutch translation against latest SVN (r656)
-
Thank you very much.
-
Hello people!
The next version is going to be released as 6.0. If you can do some last translations, please post them. Otherwise it may not be translated in this release.
Cheers.
-
There is already a partial Russian translation. Selection fit is translated there as "Заполнить выделение". It means that the selection is fitted to its content. For example if you select an object in an image that is surrounded by transparent pixels, and that the shape of the selection is the rectangle that contains the object, then selection fit will reduce the selection to be just the shape of the object. So then for example you can draw a gradient that has the same shape.
EDIT: by the way I found a bug of screen update so that you could not see what it did (it was necessary to zoom/unzoom for example to get a visual update of the selection)
-
Attached Dutch translations of r781. I don't think I will continue to have much time to work on translations, so anybody else is welcome to take over!
-
Updated Czech translation
-
Thank you very much. Your translations seem very exhaustive.
Languages done: en, fr, cs, nl, es, ar, de
Languages left: ja, pt, ru, sv
-
Hi, here is the updated and completed german translation.
-
Thank you very much. I have updated the code repository and made it online so that it updates all running LazPaint 6.2. You can check this by running the downloaded version, waiting for some seconds, and then by choosing "de" in the language list. After that, in the menu Ansicht, the item Image list is now Bilderliste, and this window is translated in german.
-
Hi,
in the "adjust curves" dialogue, the tabs have no translation string (I guess). Any chance to get them?
/cs
-
That's true. Seems like the automatic translation does not take the tabs into account. Thanks for the information.
-
For version 6.3, I have done translations in French, Spanish and German. I am not sure however if I translated correctly in Spanish and German.
Languages left: ja, pt, ru, sv, cs, nl, ar
Regards
-
It's ok, just:
"Smart zoom x3" maybe can be "Zoom inteligente 3x".
In 3d dialog:
- Flat faces: Caras planas
- Round faces: Caras redondas
- Intermediate: Intermedio
In canvas size:
- Top: Arriba
- Left: Izquierda
- Right: Derecha
- Bottom: Abajo
are not translated.
'Adjustar curvas': "Ajustar curvas"
- Red: rojo
- Green: verde
- Blue: azul
- Alpha: alfa
- Hue: Matiz
- Lightness: Luminosidad
- Saturation: Saturación
Colorize / Switch colors / Apply function:
- Correjido matiz e iluminación: "Correjir matiz e iluminación"
Shading map:
- Alpha: "Alfa"
Render: can be 'interpretar' or 'renderizar'
Image list:
- Sacar imágenes que con la casilla desactivada: "Sacar imágenes con la casilla desactivada"
(somewhere: 'cuano' -> 'cuando'
-
Thanks
-
This is the first version of LazPant translation in Latvian. It's incomplete yet but already useful.
-
Thanks, I have added it to on SVN. :)
-
New features of LazPaint 6.4 are only translated in English and French. So if you have some time and know another language, please post your language files here!
Regards
-
This basic vocabulary in Finnish
-
Thank you! :)
I am proud to have a finnish translation! It reminds me of famous demo makers Future Crew. :)
-
Hi,
here comes an update LazPaint translation in Latvian. Not completed yet, but some new 6.4.1 features has been translated and some old translations has been improved.
-
Sorry,
I could not find translatable strings for Image/Canvas size/ Anchor position list (TopLeft, Top, TopRight, etc ). :(
-
Hi,
here comes an update LazPaint translation in Latvian. Not completed yet, but some new 6.4.1 features has been translated and some old translations has been improved.
Thanks.
Sorry,
I could not find translatable strings for Image/Canvas size/ Anchor position list (TopLeft, Top, TopRight, etc ). :(
It's normal, those are not translated yet.
-
Circular, could one send you translations on an email?
Lazarus forum does not allow attachements to PMs.
-
What would prevent from posting on this thread?
-
Functional separation. Or just imagine you'd like to drop the translator a line- please update until.... or something else.
Ok, I might think of something else.
-
Hi, this is the spanish translation.
-
Muchas gracias :)
-
Hello,
There are new translation entries (just a few) in LazPaint. If you know one of these languages, I will be happy to get some help from you.
https://github.com/bgrabitmap/lazpaint/tree/dev-lazpaint/lazpaint/release/bin/i18n
Translations complete: en, fr, es
Remaining: ar, cs, de, fi, ja, lv, nl, pt_BR, ru, sv
-
Hi there.
Still hoping for some translations. If you know one of these languages, your help will be welcome.
-
I can read a bit of pt_BR but not write it... :-[
-
The link above gives 404.
I can update the nl/Dutch translation but not all in one time is that ok?
-
https://github.com/bgrabitmap/lazpaint/tree/dev-lazpaint/lazpaint/release/bin/i18n
-
@fred:
Indeed the link was broken.
Well I can only make the program update once each language, so it is simpler if you send the final translation.
-
Updated the Dutch/nl/Nederlands translation.
-
Thank you very much indeed.
https://github.com/bgrabitmap/lazpaint/tree/dev-lazpaint/lazpaint/release/bin/i18n
Translations complete: en, fr, es, nl, de, pt_BR
Remaining: ar, cs, fi, ja, lv, ru, sv
I had a query for a Chinese translation as well.
https://github.com/bgrabitmap/lazpaint/issues/40
-
Hi,
I have done Kabyle translations for Lazpaint.
lazpaint.kab.po and lclstrconsts.kab.po are in the attachment of this post.
-
Translations for minority languages - I love it!
-
Thank you very much YacineBouklif.
I've added the translation to the dev branch.
:)
-
Bulgarian translation is attached, something like 80 % done.
Validated by PO edit.
-
Thanks very much :)
-
I have done Simplified Chinese translations for Lazpaint.
lazpaint.zh_CN.po, lclstrconsts.zh_CN.po and lcresourcestring.zh_CN.po are in the attachment of this post.
-
Thanks very much indeed!
Pushed it on dev branch.
Looks great even though I can't read much of it. Though I recognized in 画布大小 that the 2 last symbols are "big-small", so that means "size". And in 向上一级目录 the symbol 上 means "up" and 一 means "one".
This translation has been requested so I'll update the issue:
https://github.com/bgrabitmap/lazpaint/issues/40
-
State of translations
Complete: de, en, es, fr, nl, pt_BR, sv, zh_CN
Incomplete: ar, bg, cs, fi, ja, kab, lv, ru
Latest translation files:
https://github.com/bgrabitmap/lazpaint/tree/dev-lazpaint/lazpaint/release/bin/i18n
Request sent to former translators for: ar, bg, cs, fi, ja, kab, lv, ru
-
Can anybody explain the meaning of “Choose entry...” and “Choose entry within file”. The menu entry is inactive and I can't test it.
-
The word „shift” has two different meanings:
1. a keyboard key (⇑);
2. a synonym for “ displacement” (e.g. colour shift).
The must be translated differently, but it's impossible. They are tied together in the LazPaint.
-
Hello Zirmeklitis
Choose entry is active with Tiff, Gif and Icon files. They can have several images within them. Though the exact meaning of the image depends on the format hence the vague term “entry”.
About the term Shift they are not confused because of the message context. rsShift is about the key.
-
[..]
About the term Shift they are not confused because of the message context. rsShift is about the key.
Hi,
Then there is problem with „lazpaint.po” file:
--- lazpaint.po 2020-03-06 20:01:31.000000000 +0200
+++ lazpaint.new.po 2020-03-09 18:46:00.535301178 +0200
@@ -3451,7 +3451,8 @@
msgstr ""
#: uresourcestrings.rsshift
-msgid "SHIFT"
+msgctxt "uresourcestrings.rsShift"
+msgid "Shift"
msgstr ""
#: uresourcestrings.rsshowpalette
-
No need as far as I know it works already. Have you tried running the software?
-
[..] it works already.[..]
It does not work for me (Fedora 28x64, Lazarus 1.8.4, FPC 3.0.4) . My suggested patch solved the issue.
-
Hi,
Here comes the Latvian translation.
Best regards,
Zirneklitis
-
Ok. Thanks.
Can you do the lcresourcestring.lv.po as well?
-
[..]
Can you do the lcresourcestring.lv.po as well?
Hi! Here it comes.
Best regards,
Zirneklītis
-
Thank you very much.
State of translations
Complete: de, en, es, fr, kab, lv, nl, pt_BR, sv, zh_CN
Incomplete: ar, bg, cs, fi, ja, ru
Replies from translators: bg
Latest translation files:
https://github.com/bgrabitmap/lazpaint/tree/dev-lazpaint/lazpaint/release/bin/i18n
-
Hello,
I have completed the Kabyle translations for LazPaint.
Best regards,
Yacine Bouklif
-
Thank you very much :)
-
Please find Bulgarian for the Beta attached.
-
Thanks. We're getting there. :)
Remaining translations to complete: ar, cs, fi, ja, ru
Latest translation files:
https://github.com/bgrabitmap/lazpaint/tree/dev-lazpaint/lazpaint/release/bin/i18n
-
Hi folks!
I've added a translation mechanism to LazPaint download site: https://lazpaint.github.io
For now, languages are: de, en, es, fi, fr.
I am looking for help to translate LazPaint download site to the language of the top downloading countries: Arabic (ar) and Chinese (cn).
Stats from SourceForge: https://sourceforge.net/projects/lazpaint/files/stats/map
Here are the current translation files:
https://github.com/bgrabitmap/lazpaint/tree/dev-lazpaint/web/i18n
Regards
-
I am looking for help to translate LazPaint download site to the language of the top downloading countries: Arabic (ar) and Chinese (cn).
Hi!
Perhaps you should put this request for support in the app in the "help" menue.
What about that?
Winni
-
Amazing job, all pages despite that they are different sites (the blog and the download site / documentation) they share the same style :)
Navigation between them is smooth.
-
Perhaps you should put this request for support in the app in the "help" menue.
What about that?
In the Help menu of LazPaint? An item like "Help to translate"?
Amazing job, all pages despite that they are different sites (the blog and the download site / documentation) they share the same style :)
Navigation between them is smooth.
Thanks. Yeah I found how to put some custom CSS in the blog. Also with Hugo it is possible to get information from a website, in this case from GitHub to generate the last changes page. :)
-
Ciao a tutti :)
allego traduzione Lazpaint in italiano, fatta "al volo" : spero sia gradita !
Hi everybody ! Here is Italian Lazpaint Translation (incomplete, about 75%): hope you enjoy !
Bye :)
-
Thank you very much :)
I've added it to dev branch.
Note that there is also an lcresourcestring.po used for translation.
Regards