Italian translation (Blender UI <2.8 and manual) #42765
Labels
No Label
Meta
Good First Issue
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Eevee & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds, Tests & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
13 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#42765
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Traduzione in italiano dell'interfaccia di Blender fino fino vers. 2.79 e del manuale
Blender UI (before 2.8) & manual Italian translation
Changed status to: 'Open'
Added subscriber: @blend-it
Info di servizio
La traduzione italiana è in continuo aggiornamento, generalmente con una cadenza maggiore di blender nel suo complesso.
L'ultimissima versione della traduzione italiana è il file saricabile al link https://svn.blender.org/svnroot/bf-translations/trunk/locale/it/LC_MESSAGES/blender.mo
Tale file va sostituito a quello di default presente nella cartella di installazione di blender /2.xx/datafiles/locale/it/LC_MESSAGES/ (dove 2.xx è la versione installata).
Nota che in prossimità del rilascio di una nuova versione di Blender usare versioni molto recenti della traduzione può comportare problemi (solo di traduzione!) in quanto alcune traduzioni possono essere variate e/o riguardare solo la nuova versione in corso di finalizzazione anzichè quella stabile più vecchia. Se riscontri questo genere di problemi (menu, descrizioni ecc ecc. prima tradotte che ritornano ad essere in inglese), è sufficiente ripristinare la versione precedente del file blender.mo (di cui conviene quindi fare un backup prima di sovrascriverlo).
Se riscontri errori di traduzione puoi segnalarli registrandoti e scrivendo un post qui sotto.
30/11/2014
how to post updated .po file?!?
fix it translationto fix IT translationChanged status from 'Open' to: 'Archived'
Added subscriber: @mont29
Please have a look at 'Translation' project (https://developer.blender.org/project/view/4/), everything is explained in pages linked there.
sorry but I don't understand how to upload updated .PO or .MO files, and the present translation contain a lot of bad mistakes (some Msgids are translated in complete non-sense way, and sometimes the command result is the opposite of that translation show... :-( ).
I'm a translator, not a coder... the pages are very cryptics ;-)
blender-po-mo.7z
attached, updated PO and MO for italian language.
Please add files at well location
thanks
Changed status from 'Archived' to: 'Open'
OK thanks, will do.
many thanks... :)
some questions:
See you
Hey blend-it, committed your first update.
it3206-po-mo.7z
New PO-MO.
Fixed some totally wrong error messages and other stuff.
Thank you :)
Thanks again (btw, no need to send .mo, that is auto-generated by our scripts, only need the .po one ;) ).
Ok, I'm still learning how entire system work, so sorry if I importune you with my perhaps stupid questions ;)
At the bottom of my po, there are some commented msgid and msgstr without a src: string... so I think this is stuff that I can remove... it's right? And what produce this stuff it's here? It's poedit, some automatic server procedure or something other?
Thanks for you patience! :)
No problem, much better to ask questions than break something (or waste time uselessly) ;)
yes, update scripts manage all that stuff, so you have nothing to do here. Since I committed your po before doing the weekly update yesterday, current it.po in SVN is perfectly up-to-date and in sync with the ref .pot file. In any case, lines like src: foo.c are just mere comments, only here to help translators to get context from code if needed, gettext translation code itself do not use them.
Yes, .pot is the reference here, but again, you should not have to do anything anyway.
Yes, you can clean them off. they are the messages that existed in previous version of the translation, but are no more needed in newest ones, scripts comment them rather than just deleting them.
Looking .po with a plain stupid text editor I've noticed that poedit (or notepad++?) sometime split quoted strings in 2 or 3 lines (the first only with "") and sometime join 2 src: lines by removing a CR and the next line #:, so two src: lines becomes one only... :-
I hope it's not a problem for scripts.
Attached, last .po
bye :)
it.zip
Thanks, committed. :)
Oops. it's old, now I have a new one! :)
it.zip
Committed ;)
thanks :)
Joyeux Noël
Cause I see that 2.73 is already in RC, I attach latest .po as you can include (if possible) in next official release :)
it.zip
ps: for the future, I need context for "frame" term... frame as part of video and frame as border of something... there are non way to distinguish in present .pot :(
Eeeeh, no, translations are locked down now for 2.73, like everything else. Will go in master later today, will be for 2.74 now. ;)
As for contexts… I know we would need those in quite a bit of places still, but afaik that kind of changes in UI code is still frozen…
Committed. :)
Sorry last PO cause a blender crash when launching a render with internal engine (not with cycles). ?:-(
Attached the fix.
The (stupid) difference is in #: source/blender/editors/render/render_internal.c:400 translation where I used a %s instead of %d :-
it_fix.zip
For context, I remember a spreadsheet on googledocs for this kind of problems, but I don't find it... For now I've found serious context problems with "light", "frame" and "clip"
it.zip
new .po
for contexts how I can help?
Not much to do… You'd need to convince other devs around this is important etc. ;)
hmmm.
some changes are very easy.
e.g. both
have as msgid "Light", but the first is "lamp" and the second is the opposite of "heavy"...
The solution it's easy because this is a little mistake by coder:
have a msgid "Light Group:" and I think that also "Light" in #: scripts/startup/bl_ui/properties_render_layer.py:86 have to be changed in "Light Group:".
This kind of changes are easy and trivial...
More complex for "clip" (used for "video" and for "cut"...) or "Frame" ("part of video" and "box/border")... :-( Now the result it's a ridiculous drunk translation in some places...
How and where I can "push" for solution? ;-) I have to open another task?
Added subscriber: @GabrielGazzan
I have years, now, trying to get someone to fix some of these problems too.
Reality is:
nobody is taking active care for these kind of problems in Blender UI
:-/
If you want to try something, you can start a new bug report, and assign it to UI team…
@GabrielGazzan: after 1 month of translation, I can affirm that the care about linguistic coherence in original strings it's far to be good... :-(
See the case of "clip", "light" or "frame", but also similar functions are differently named in different places or at the opposite different stuff it's similar named...
So, I don't like it, but if I wont to fix some linguistic bugs, I must become a "coder" and not only a translator...
where are the problems you find? IT and ES (right?) are quite similar so perhaps we have similar problems...
@mont
I've find how to fix the "light" problem in scripts/startup/bl_ui/properties_render_layer.py:86, locally on my installation, and it work! It's very trivial and I do it using "edit source" context menu, so no compile/C/make/build/strange stuff... simply easy plain text... wow! :)
How I can submit a patch for this? I have to submit the entire properties_render_layer.py script someware or there are a different way to do it? I post here, or what?
Sorry for my stupid boring questions... ;)
Thing is, all those kind of fixes (involving contexts) are freezed since two years or so now. Fixing the issues is usually trivial, but my suggestion was to make a report to ask for un-freezing this aspect of i18n in Blender. I have no time or energy to spend fighting for this myself tbh, but would be happy if this was unfrozen (never really understood that decision in the first place), and then we could resume fixing names 'collision'…
Btw, here is the ML thread about that freezing: http://lists.blender.org/pipermail/bf-translations-dev/2013-March/000424.html
PS: more technically, to submit a patch you need to make a diff against master code (i.e. org code), and submit that diff here on the tracker (https://developer.blender.org/differential/diff/create/). But again, this is not so useful in this case, as you said it’s 99% of cases very trivial, so just noting the issue is usually enough.
We had a googledoc listing all those back in the days, https://docs.google.com/spreadsheets/d/1Ud7oYedKWrkzdtQGp_BNgPurtroBAiRxWGn-Ewhbjzw/edit#gid=3, then I went over reported issues from time to time and made a 'batch' commit (to avoid tens a one-line commits each time an issue is reported ;) ).
Added subscriber: @ZhangYu
I think something like context-based solution cannot be safe enough to fix all problems like this, since this is a caulture-related issue, which means, different language speakers would face different polysemy issues on different words, For example, based on most of the polysemy words for Chinese tranlation, I've listed them in the google doc, but we know that no one can guarantee that new problems will not occur, as I said, it is culture-related issue.
IMHO, a mapping-based system would be ideal to fix it, which leaves translators the ability to choose which map is suitable according to their specific language(s). I don't think this would be easy to do. Or devs got other big and better plan. :)
@mont29: ok, task blender/blender#43295 submitted.
@ZhangYu: of course it's a "cultural" problem. But I don't ask for singular/plural or male/female/neutral forms, but for real strongdifferent significant... "cut" it's not "video segment", so "clip" it's strongly bad word to use without context care! :)
About different ways for implement translations, I nothing know about this... Of course gettext that translate same string everyware it's not 100% safe, but change the system now I think can be enormous task for devs... I hope context can be a good middle-way.
new update for it.po :) it.zip
Updated repo. :)
@mont29
There are a server script that apply the poedit's "translation memory" or something similar (trying to extrapolate new translation from existing ones) in files that I send?
I have strange sensations about "fuzziness" in the file from branches! :-)
many thanks
Yes, each time po's are updated from master, it tries to find 'similar' messages and give them existing translations (tagged as fuzzy, so that this does not end in actual mo translation files). Some times annoying, but also sometimes useful, when only a small detail changed in source (like adding or removing a column), avoids you to have to retranslate from scratch…
If possible, I prefer this kind of scripts are not applied to it.po.
In this file there are a lot of old strings translated this way and de-fuzzed by some previous (bad) translator(s) without check if auto-translations was good. :-|
(it seem that a search-and-remove procedure was applied to simply clear all fuzzy tag, just for show an apparent progression of translation work... BTW, it will be interesting to know when and who...)
So now, each time auto-translation script run, this shit is spammed everywhere...
I've already removed a lot of this stuff, but this auto-fuzzy-multiplication IMHO don't help to maintain a clean file, because "auto-translations" are mixed with "original string changes" what I have already reviewed but that return to be "fuzzy"...
+1. I think I had some talk with Bastien about this last year, but I didn't get chance to prove it at that moment. And, more important, considering the polyseme issue (which drives me mad), a good translator should have all fuzzy strings RE-CHECKED to use the most suitable translation based on the corresponding path/function, to make sure it will not look too stupid on UI.
I think everyone prefers a workflow where you first fix the few fuzzy-changes, and only after runs locally autotranslation and review fuzzy-auto, if desired :-)
PS: that about context/T43295? Who have to decide what?
new it.po
it.zip
committed, thanks. :)
new po
I try to download it after committing to fix new strings for 2.74.
Deadline is 8/3, isn't?
it.zip
Thanks, committed. :)
As for deadline… in theory, yes, 8/3, but this is quite unlikely. We'll make a testbuild today or tomorrow, usually there's at the very least two weeks before first testbuild and first 'beta' one (which defines freeze of translations). ;)
it.zip :)
edit 6-3-15 - fix zip file
Thanks, committed.
latest for now :)
it.zip
done :)
fix IT translationto IT translationnew little fixes :)
it.zip
(updated 2015-04-09)
new :)
it.zip
done :)
in the header of po file 3466 contain
"Project-Id-Version: Blender 2.73 (sub 8) (b'00a3c9a')\n" and
"POT-Creation-Date: 2015-02-16 20:44:07\n"
strings...
It's ok for 2.74, or something is wrong? ?:-)
POT have to be refreshed to have all latest translatable strings for 2.74?
thanks :-)
I partially auto-reply to my question.
I've updated the PO with latest POT in https://svn.blender.org/svnroot/bf-translations/trunk/po/
and also if blender version in header still remain 2.73, pot string become "POT-Creation-Date: 2015-04-13 21:01:13\n" and some new strings magically appears ;-)
new po with full orthographic check
it.zip
committed, thanks. :)
updated PO :)
it.zip
Done, thanks.
new po updated with 3562 pot :)
it.po.7z
Done, thanks.
thanks to you :)
A question. What's the deadline for updating po's for 2.75 final release? I need it to schedule my work on :)
No idea really, think we'll do a first RC soonish (end of week or so?), which is usually the point where I freeze translations for a given release…
Ok. in the next days I will try to upload little updates more frequently :)
it.zip
I´d be very useful to have some kind of alert about when the exact date will be.
At least a week before or so.
That way one could set appart time before that to complete the task.
just a thought
@blend-it done, thanks.
@GabrielGazzan good point.
new one :)
I upload frequently/daily because I don't know the day of freeze.
You can commit only the more recent before the freezing, instead each one daily.
many thanks :)
it.zip
This comment was removed by @blend-it
This comment was removed by @blend-it
it-.zip
updated 11/6/2015
it seem already all freezed... :(
it.zip
yes it is - but your 11/6/2015 version got in ;)
whats good because I fixed some errors in Sequencer and Video clip editor...
But in RC, fixes are not present... ?:-|
Eeeeh… you’re sure about that? Can you check https://developer.blender.org/diffusion/BT/browse/master/po/it.po has your fixes?
Hmmm the file you linked, when downloaded, take 24.4 MB, mine about 3.8... what?
The size increase each time I've try to download... now I'm on updated linux machine... I don't think it's my client problem, perhaps some script is running on server...
also fr.po is 24.6 MB now...
now, the download is about 15MB... what happens?
new PO
it.zip
summer PO ;)
it.zip
done :)
This comment was removed by @blend-it
update with some strings for 2.76 (pot3790)
as requested in june, some idea about freezing day?
it.zip
Well, sent a mail on monday… I know should have been done sooner though.
You're lucky, we are about to tag, your update is just in time to be integrated. :)
Thanks :)
For non-coding people like me, translate Blender is quite similar to the paradox of Achilles and the tortoise ... :-D
With as lot of untranslated and fuzzy strings in my .po, I discover new features/strings only when builds are done or from release notes...
https://builder.blender.org/download/
In the link above you can download the most recent development builds of Blender to see the new features in action. ;)
When translating a new feature, you can also check other latin languages PO files to see how they've been translated (if they already are) and that way have a clue of what kind of feature it is.
new (3802)
it.zip
@GabrielGazzan ok thanks. Sometime I've already looked at fr and es translations, but some strings are still cryptic for my or for other translators. Sometime I have a different interpretation of what a command do (or if it's buggy)... :D
There are also some abbreviations that will be easy to translate if the entire string was in comment (trivial example R for red, H for Hue...)
Done :)
thanks :)
it.zip
Done :)
some fixes in armature/pose/rigging area etc.
;)
and more (edited 5/10)
it.zip
done
various fixes
it.zip
Done
various fixes in gpencil and more
it.zip
done.
it.zip
technical questions:
because I still use strings from pot rev3812 for 2.76. Newer ones introduces in some strings differences that results (I think) in translation regression for 2.76...
Many thanks :-)
Done.
All POs are always cleaned up and updated before going to
/trunk(and hence, being compiled as MOs). And no need at all to keep to 2.76 version, we are now again working on plain master of Blender, compatibility with 2.76 is no more required at all.There should be no difference at all (not even sure why we have that one twice actually…).
one year and more of translations :)
it.zip
when next blender release is ~planned?
thks!
Added subscriber: @Blendify
2.77 is the next release. Then 2.8
Removed subscriber: @Blendify
Done.
2.77 is due end of january, early february (if there’s no delay… :| ).
ok, thanks :-)
I think to plan next PO for 15-20 January.
Question:
To "live-check" new translation for 2.77 I have to use vanilla builds , not gooseberry-branch ones, right?
I've not found stupid-users-dedicated info about this 2 blender flavours...
New PO for 2.77
it .zip
news about freezing?
new :)
it4.zip
2nd upd. 2015/01/27
Well, we should go in bcon3 next week or so, and then it’s supposed to be less than a month before release - but in practice it had been quite a bit longer recently. :|
boids and nodes fixes
it.zip
Latest. Thanks :)
it4083.zip
It's already all freezed?
it4088.zip
it.zip
new
it.zip
upd. 24/02
Added subscriber: @lcsmf
Removed subscriber: @lcsmf
new 14/6/2016
it.zip
new little fix
it.zip
new for 2.78
A lot of micro-changes in strings... :-
it4309.zip
new
it.zip
when freeze for next release is ~planned?
thks!
This comment was removed by @blend-it
This comment was removed by @blend-it
This comment was removed by @blend-it
This comment was removed by @blend-it
This comment was removed by @blend-it
This comment was removed by @blend-it
This comment was removed by @blend-it
This comment was removed by @blend-it
it.zip
it.zip
perhaps it's all already freezed but...
Added subscriber: @umarabdullahi-2
please approve i want to translate blender to my language "Hausa"
last fix for 2016 and happy new year :-)
it.zip
Lot of fixes
it.zip
Added subscriber: @davide97
This comment was removed by @davide97
blender è un sw parecchio complesso, e la traduzione segue precise terminologie per garantire uniformità e coerenza dei comandi. Da quanto lo usi? dove trovi problemi con l'attuale traduzione? hai già tradotto altri sw?
Lo uso da tre anni;
L'attuale traduzione diciamo che non ha dei problemi seri, quello che propongo é di cambiare alcuni suggerimenti con riferimento al manuale o ad altre risorse attendibili;
Ho tradotto Artweaver 5.
Ecco un mo (del po sbagliato, ma è solo dimostrativo)blender.mo
se mi dici quali suggerimenti trovi errati e come li modificheresti capisco meglio.
il MO allegato non ho capito cosa sia. quello di blender è attualmente di circa 1.4MB, il tuo di 40k cosa sarebbe? e cmq è più utile allegare un PO.
servirebbe molto che qualcuno prendesse in mano la traduzione del manuale, che attualmente in italiano non c'è.
https://docs.blender.org/manual/en/dev/index.html
qui https://docs.blender.org/manual/en/dev/about/contribute/index.html la spiegazione di come procedere.
it_alt.po
Eccolo, si perché qui ci sono solo le mie proposte
Sarebbe interessante, mi renderò utile traducendo il manuale
Prendo per riferimento la lingua di default o la traduzione in italiano, del programma? (per i comandi)
Sarebbe utilissimo, perchè la traduzione è proprio inesistente, e blender come sai non è molto userfrendly, quindi avere spiegazioni dettagliate nel manuale è davvero utile.
Per i comandi naturalmente bisogna riprendere esattamente la traduzione italiana del programma, altrimenti gli utenti non capiscono un tubo!
ps: al PO ci do un'occhiata al più presto.
Ok, ti consiglio di guardarlo solamente... cioè non farci operazioni, perché è diverso dai tuoi (ho scaricato anche l'ultimo dei tuoi di questa pagina, quello che ti ho mandato proviene dalla cartella /branches dell'archivio)
Se ritieni l'idea buona, modifica le stringhe nel tuo po e fammi sapere, così saprei se continuare (continuiamo insieme)
Per il manuale quindi dipende da questo, si vedrà allora
Ad esempio io distinguerei il Mirror nel tab strumenti dal modificatore, chiamando il primo "Rifletti" e il secondo "Specchio"...
Oppure Calotta > Emisfera, Faretto > Spot; Lamp in ogni caso Luce....
Quando non necessario lascerei comunque tutto minuscolo, mettendo l'iniziale maiuscola solo per indicare qualcosa di specifico....
Alcune parole le lascerei in inglese, tipo keyframe, keying set... sarebbe più efficace...
E altro che ancora non ho fatto, quel po come vedi è per la maggior parte bianco, in effetti meglio, così vedi subito gli esempi
Sto guardando le modifiche ma ci vorrà un po' perchè trovare le differenze è piuttosto macchinoso. Alcune cose però non vanno:
Altre stringhe le ho inserite, altre le verifico con calma.
Cmq x evitare casini mi sembra meglio se traduci il manuale così puoi fare una descrizione dettagliata dei comandi cosa x cui mi sembra che sei portato!
Hai ragione su tutto, solo il fatto del Mirror non mi convince, perché se clicco su Specchia (comando) mi si riflette l'oggetto in base all'asse che pigio sulla tastiera, mentre il modificatore mi specchia l'oggetto su cui lo applico rispetto a un'oggetto che scelgo... il secondo sdoppia, mentre il primo semplicemente riflette.
Per il fatto della primitiva, si ho sbagliato xD
Dipende da cosa posso fare nel manuale, deve essere una traduzione precisa dell'originale inglese? O posso eventualmente aggiungere (o rielaborare) le descrizioni, etc...?
Gentilissimo comunque per la risposta :D
Navigando ho visto che quello inglese ancora non è completo, in alcuni voci c'è scritto ToDo
hmm anche tu hai ragione... potremmo usare specchia, ribalta e rifletti a seconda dei casi.
il problema è se si può davvero fare, perché se in inglese c'è mirror e l'interfaccia è stata pensata con mirror, bisogna vedere dove finiscono le traduzioni e se la stringa non è condivisa in più posti. Insomma, i sinonimi (italiani o inglesi) sono cose molto pericolose e non sai mai che non salti fuori qualche megacazzata.
per dire, un caso analogo è "frame" che è sia cornice che fotogramma, qunindi non si può tradurre altrimenti in metà dei posti sarebbe ok ma sbagliato nell'altra metà (ed a scovarle...) :-(
lo stesso era x light (leggero e luce).
E' un vero casino.
Cmq vedo di recepire il tuo suggerimento se è fattibile :-)
X il manuale, io partirei dall'inglese x avere una tarccia, ma se alcune frasi sono troppo sintetiche e non si capiscono, e vuoi spiegarle meglio, non vedo il problema, purchè tu sia sicuro che in effetti la spiegazione che aggiungi sia giusta e blender faccia effettivamente quello che tu scrivi!
edit
come temevo, se Mirrorlo cambi da una parte si incasina altrove. Ho corretto il suggerimento con "Ribalta bla bla bla..." e il messaggio della barra di stato "selez. asse di ribaltam. xyz", di più non si può fare. :-(
purtroppo coi sinonimi è così, per non dire che a volte in inglese verbo=nome (mirror è proprio tipico). Tradurre bene è più difficile di quel che sembra :-D
Removed subscriber: @umarabdullahi-2
@davide.baldo.88 Tripepi (davide97)
Are you ready for the manual? :-)
Here you can find the PO files to be translated: you can download, translate the strings, and upload here (better if in a periodical, cumulative .zip file).
I already partially worked on Glossary , terms (to reflect the UI), but definitions have to be translated.
Contrary to what I said in previous post, the basis is the english version, so the translation have to be quite near the original text (obvious, due to the work based on .po files). So only small variations are possible, sorry.
Ok, that's all, it's your turn! :-)
ps: administrators said me that is preferable to use english here.
Sorry but I don't want to translate the manual anymore...
Also, unfortunately now I have no time to do this work
Actually through the internet people can find tutorials and videoguides (in italian!)... so this translation could be a little useless, although it is of the official manual
I don't think so, but it's your choice...
Added subscriber: @CarloBergonzini
Hello,
I'm an italian blender user and in my free time I would be happy to help in translating the manual.
It's first time I approach the subversions management problem, so I followed the steps descripted in the guide until I was able to get a copy of the translation on my pc and now I would like to have a feedback before taking any step further. As far as I understood I need to edit and save the .po and then commit them for administrator check, right? Am I missing something? How many files do you usually edit before committing?
Hi @CarloBergonzini, sorry for the late reply I have been sick/busy. Becuase there is not really a large number of people working on this having people review translations is not really possible.
Yes but after they are committed they are not checked but go live on the online manual as soon as it is built.
You will need commit access which I will give you after typing out this reply. The login credentials are synced with this website.
It does not hugely matter as long as you go long periods without committing. This can result in merge conflict which are a pain to manage. I would try to stick to committing every time you finish a folder of files or any large files.
Added subscriber: @Blendify
Thanks for the reply @Blendify. I'll do my best.
I hope you'll have time to check if I'm committing the version files in the right way and not messing things up for at least the first commit.
I will make sure to check.
Added subscriber: @aleppax
@CarloBergonzini
Hi and thanks to take care about manual.
Please make sure that the terms you will use in the manual are the same the Blender UI use.
I've translated the Glossary and a lot of titles (skipping the body of the text) for this reason, but the work is far to be completed, so, pay attention to the coherence and feel free to ask! ;)
I'll make sure of that @blend-it! I've start tackling the job, but I feel a little bit unsure about how to properly translate the pages.
From a brief research I've found out this guidelines: https://wiki.blender.org/index.php/Meta:Guides/Translation_Guide. Are they the only source of wisdom on the topic?
Is there a better section to start with? My first attempt was on the "text" section, and to be honest is taking more time I expected. Are you suggesting to first working on the titles and only then on the body?
Also it's not quite clear to me if it is appropriate to translate the Blender UI words. While in the glossary they are useful to quickly understand the italian translation, in the other pages seems the least importan things to me. Take for instance the page about "Empties": is calling them "vuoti" really helping the reader/user? In my mind it seems more helpful to refer to them with the name they see in the UI. So I would have focus on the body, the instructions on how to use them, rather then the titles. But it's just my first thought, maybe it would took to much time to do everything this way. What's your opinion?
For this, it's better to ask @Blendify
I think it's better to start with "easy" arguments for blender's newbies, interface, modeling, etc, but it's my idea. If you prefer to start with bones, camera tracking, VSE or game engine, feel free to start where you want. I think is better to translate arguments that you know and tools that you really use, to avoid misunderstandings in the translation (this is the policy that I use for myself... if you use, you know).
Perhaps you think at the "Italian manual" as a reference for the "English UI"... But is intended as the reference for the "Italian UI"! And in the UI the "Empty" is translated as "Vuoto", so the reader/user actually find the corresponding term (is for this I've started with the titles). ;)
If peoples use English UI, they can also understand and use the English manual!
If you focus on the body, it's good, because I'm focused on the UI (and consequently on the titles ;))
Keep in mind that usage of English terms in Italian UI is reduced as far as possible: if people prefer the English term for something (command, etc), they can use the English language for the interface instead.
Added subscriber: @MicheleBedendo
Changed status from 'Open' to: 'Archived'
I am going to close this, if there are questions on translations these can be on a new task.
hmmm, it's easiest to monitoring only this task for new posts, instead of checking always all if there are question about this translation...
I will prefer if this one can stay open.
IT translationto Italian translation (Blender UI and manual)Changed status from 'Archived' to: 'Open'
I will leave open for a bit longer.
Removed subscriber: @mont29
Added subscriber: @nokipaike
@blend-it vorrei dare una mano nelle traduzioni e con il manuale in italiano..
piccoli compiti da eseguire..
@Blendify I would like to help with the manual, small tasks
Grazie. Il manuale necessita di un bel po' di lavoro, se riesci a metterci mano sarebbe molto utile!
Italian translation (Blender UI and manual)to Italian translation (Blender UI <2.8 and manual)Changed status from 'Open' to: 'Resolved'
Due to hw incompatibilities, for now I can't work on 2.8.
I will restart on 2.8x series after upgrading my hw. See you.
Added subscriber: @jabbar12
Translation services here