Hello,
I have a little provocative question. Do You (developers, maintaners
and translators) think that we need help texts in Yast?
Do You think that sentences like:
"<b>FS Type</b> shows the file system type."
or "Press <edit>, to edit NNNN, <add> to add NNNN and <delete> do
delete the NNNN."
will really help the user? ;-)
Unfortunately big part of Yast help looks like this...
I personally see it as a lot of work for maintaining and translating,
but in the end it brings not much...
Is it maybe a rule, that every UI element needs some description or something?
What do You think?
regards,
Wadim
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-translation+help(a)opensuse.org
I want to know if I keep on translation those po files of lcn and yast,
Are there any chances these strings can merge into 11.1-final ?
If yes, when will be the deadline?
Thanks for answering
With Regards
Ray Chen
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-translation+help(a)opensuse.org
The final(?) YaST merge for 11.1 RC1 is running. I think are only a few
and minor string changes (for important bug fixes and enhancements,
though).
I'd like to start preparing the yast2-trans packages around 13:00 CET.
Drop me a line, if you need more time.
Cheers,
Karl
--
Karl Eichwalder
R&D / Documentation
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-translation+help(a)opensuse.org
Hi,
In the .po files updated today, there are 2 strings in yast2-gtk.$$.po
which are really big:
line 677:
<h1>Purpose</h1><p>This tool gives you control on overviewing and
picking patches. You may also reverse patches that have been applied
to the system.</p><h1>Usage</h1><h2>Categories</h2><p>Patches are
grouped as follows:</p><ul><li>Security: patches a software flaw that
could be exploited to gain restricted privilege.</li><li>Recommended:
fixes non-security related flaws (e.g. data corruption, performance
slowdown)</li><li>Optional: ones that only apply to few
users.</li></ul><p>Only patches that apply to your system will be
visible. openSUSE developers are very restrained in pushing patches;
you can be sure that all patches are of signficant severity.</p><p>If
you are looking for applications enhancements, you should check for
Upgrades on the Software Manager.</p>
line 673:
<h1>Purpose</h1><p>This tool lets you install, remove, and update
applications.</p><p>openSUSE's software management is also called
'package management'. A package is generally an application bundle,
but multiple packages that extend the application may be offered in
order to avoid clutter (e.g. games tend to de-couple the music data in
another package, since its not essential and requires significant disk
space). The base package will get the application's name, while extra
packages are suffix-ed. Common extras are:</p><ul><li>-plugin-:
extends the application with some extra functionality.</li><li>-devel:
needed for software development.</li><li>-debuginfo: needed for
software beta-testing.</li><li>-fr, -dr, -pl (language siglas):
translation files (your language package will be marked for
installation automatically).</li></ul><p>You will find both packages
installed on your system, and packages that are made available through
the setup-ed repositories. You cans either install or upgrade an
available package, or remove an installed one.</p><blockquote>A
repository is a packages media; it can either be local (like your Suse
CDs), or a remote internet server. You can find utilities to setup
repositories on the YaST control
center.</blockquote><h1>Usage</h1><h2>Available, Upgrades, Installed
buttons</h2><p>These buttons produce listings of the different sources
of packages. 'Available' are the ones from the setup-ed repositories
less those you have installed. 'Installed' lists the packages
installed in your system. 'Upgrades' is a mix listing of the installed
packages that have more recent versions available. 'All' will combine
all sources.</p><h2>Filters</h2><p>Enter free text into the
search-field to match their names and descriptions. (a search for
'office' will bring up the 'OpenOffice' packages as well as AbiWord
which carries the word 'office' in its description). You can also
choose to view software from a specific repository.</p><h2>Categories
& Collections</h2><p>Software for openSUSE is indexed so that you
can find software for a specific task when you don't know the name of
the software you are looking for. Browse indices of software by using
the tree-view in the left column; you can view the available software
by their Package names, or grouped in 'Categories' or 'Patterns' by
the selecting a view-mode from the drop-down-menu below. Categories'
are simple, hierarchical classifications of software packages, like
'Multimedia/Video', while 'Patterns' are task-oriented collections of
multiple packages that install like one (the installation of the
'server'-pattern for example will install various software needed for
running a server). By using 'Install All' you make sure that future
collection changes, when you upgrade openSUSE, will be
honored.</p><h2>Software details in the box below</h2><p>In the
package detail view you can perform actions affecting this software;
like install, uninstall, version-upgrade or -downgrade. All changes
that you make will be saved, but not yet performed.</p><p>You can
review changes in the right-side pane of the software-manager. You can
revoke changes individually at any time by clicking the 'undo'-button
next to a saved change.</p><p>The lock button can be used to lock the
selected package state; it won't allow some automatic operation to
install, upgrade or remove the package. This is only useful in very
unusual cases: for instance, you may not want to install some drivers
because they interfer with your system, yet you want to install some
collection that includes them.</p><p>The changes will be performed
once you decide to click the 'perform changes' button in the
lower-right corner. If you want to leave the software-manager without
performing any changes, simply press the button labeled
'Abort'.</p><blockquote><i>Developed by Ricardo Cruz
<rpmcruz(a)alunos.dcc.fc.up.pt><br>Thanks to Christian Jager for
co-designing this tool.</i></blockquote>
by the way, in the bigger, sometimes it calls openSUSE, in other Suse....
It is a help text or a manual itself ? >:-)
Regards,
Luiz
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-translation+help(a)opensuse.org
Hello,
Could any translation responsible check for that bug:
I've got this gnome menu translated since 2 releases of openSUSE for
nothing, they're note shipped in the translation packages... (the mo
file isn't isntalled)
It doesn't make sense to give a translated distro if the main menu
appears in English.
I made much effort to translate more gnome things for 11.1. Please,
help to make this work valuable.
https://bugzilla.novell.com/show_bug.cgi?id=438980
Cheerio,
Djan
wa-team coordinator
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-translation+help(a)opensuse.org
I am sorry to do this but I had to check in an updated gnome-packagekit.pot
file today. There were some last minute changes that really needed to go
in.
There was a memory leak introduced in already accepted code that was
concatenating strings together via strdup_printf and returning them from a
function that was supposed to return const pointers so they were never
freed. In order to fix this some strings had to redone (git commit cd466f
- fix last python commit else we leak memory). And there were evidently
some strings left that were missed and not marked for translation (git
commit 408167 - mark some strings as translatable). Finally some additional
and better error strings were added that will help diagnose problems.
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-translation+help(a)opensuse.org
Please, fix your files. I already checked af and xh.
--
Karl Eichwalder
R&D / Documentation
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
Hi list,
In french, Networkmanager in KDE4 is only partly translated and is mostly in english. I opened a bug: https://bugzilla.novell.com/show_bug.cgi?id=447077
Did you have the same probleme in your language or only french is affected?
Cheers,
Guillaume
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-translation+help(a)opensuse.org
Hi all,
I'm translating into Italian the lnc/po/update-desktop-files-kde.it.po file. Watching the changes between my last version (39512) and the svn head (41534), besides the fuzzy and untranslated strings, I've discovered a lot of new/modified translated strings with errors or strange behaviors.
In fact, I've found mainly these problems:
- some strings are translated into different strings even if they are relative to the same msgid of the same file
- some new and modified strings contain grammar mistakes or do not match the singular/plural of msgid (while original translations was right)
- some translated strings are replaced with untranslated ones
- some translated strings are replaced with wrong ones
- some modified strings seems to be replaced by strings generated by an automatic translator
- some modified strings contain words that do not exists in Italian
- some modified strings do not follow standard Italian translations (see http://en.opensuse.org/Translation-it#Elenco_delle_parole_di_uso_comune_e_l… )
- some modified strings contain fuzzy words or now they are ambiguous
Are the above problems specific for Italian translation or they occurred also for other languages? And only in update-desktop-files-kde.it.po file or also in other update-desktop-* files (I've not checked them because they are not assigned to me)?
Another thing: what is the better thing to do now? Check the whole file looking for strange/wrong strings (because problems are inside the "translated" strings, and they are a lot) or only the strings changed by last commits? This because there is few time to correct the above problems before the next packaging...
Regards,
Andrea
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-translation+help(a)opensuse.org