similar to: RFT: Use Greek semicolons for comdlg32's printer status enumeration?

Hi, Could any of you help me to localize the `centos-art.sh' script into different languages? The infrastructure for doing it is already in place and quite automated. All we need is that you translate strings from English to your own language in an interface like the following: #: trunk/Scripts/Bash/Functions/Render/Svg/svg.sh:54 msgid "Saved as" msgstr "" In this

Hi, I am new to Ruby/Rails but totally fall in love with :D Nonetheless, today I am totally stuck with Ri18n. I basically followed the 10 Steps to Make Your Rails Apps Multilingual. No errors are thrown, the english version works as before with the freshly added <%= _('''') %> Still, no translations are performed. Setting I18nService.instance.lang = ''de''

Hi, I am trying to use the gettext() function to translate some text. I have never used this function before, so, it's entirely possible that I am doing something wrong. The issue that I am encountering is that gettext() properly translates some text, but not some other. Natural language was compiled in my R (installed from the Debian repositories): $ R R version 2.15.1 (2012-06-22) --

Hi, I am trying to use the gettext() function to translate some text. I have never used this function before, so, it's entirely possible that I am doing something wrong. The issue that I am encountering is that gettext() properly translates some text, but not some other. Natural language was compiled in my R (installed from the Debian repositories): $ R R version 2.15.1 (2012-06-22) --

Below is a patch for setwd() to show path in error message. Current it just gives error messages such as: Error in setwd(libdir) : cannot change working directory with the patch it should (read untested) give: Error in setwd(libdir) : cannot change working directory to 'path/that/fails/' PATCH: % diff -u util.c "util,patch.c" --- util.c 2012-12-16 13:13:05.002249900

Dear developers, I found a small typo in the german translation for the aggregate() function: In the string "keine Zeile f?r die Aggragation" it should be spelled 'Aggregation' instead of 'Aggragation' (e instead a). After a quick look into the sources, I found two places for it: #grep -r -e "Aggragation" * src/library/stats/po/R-de.po:msgstr "keine

This patch makes Perl strings translatable. The Perl strings end up in the PO files as usual. It does not touch the embedded POD. Internationalizing the Perl strings was pleasantly simple. Just add: use Locale::TextDomain 'libguestfs'; at the top of any *.pl or *.pm file. Then for each string in the file that you want to be translatable you place TWO underscores before it: -

data/Makefile.am | 8 ++--- player/swfdec-player.ui | 22 +++++++------- player/swfdec-window.c | 2 - po/POTFILES.in | 1 po/POTFILES.skip | 1 po/fr.po | 72 ++++++++++++++++++++++++++++++++---------------- thumbnailer/Makefile.am | 20 +++++-------- 7 files changed, 74 insertions(+), 52 deletions(-) New commits: commit

I noticed that virt-v2v, which is written exclusively in perl, failed to generate virt-v2v.pot. After much head scratching I also noticed that libguestfs.pot didn't include any messages from perl sources. Some reading of libintl-perl shows that a somewhat more complicated xgettext command line is required, as it doesn't understand Locale::TextDomain syntax by default. After a little more

When building the latest svn source of vorbis-tools, I get the following error: Making all in po test ! -f ./vorbis-tools.pot || \ test -z "be.gmo cs.gmo da.gmo es.gmo fr.gmo hr.gmo hu.gmo nl.gmo ro.gmo ru.gmo sv.gmo uk.gmo" || make be.gmo cs.gmo da.gmo es.gmo fr.gmo hr.gmo hu.gmo nl.gmo ro.gmo ru.gmo sv.gmo uk.gmo rm -f be.gmo && /usr/local/bin/msgfmt -c --statistics -o

po/LINGUAS | 2 +- po/pl.po | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 62 insertions(+), 1 deletion(-) New commits: commit 54a78d5fda9973f9db36d164f09746fe18607043 Author: Jakub Bogusz <qboosh at pld-linux.org> Date: Sun Dec 16 22:28:25 2007 +0100 add Polish translation diff --git a/po/LINGUAS b/po/LINGUAS index a1bece0..fe71204

These patches combine HVSource and HVTarget into a single Converter. This should make it more obvious where to hack without losing any practical flexibility. GuestOS remains separate. GuestOS is now a misnomer, because it's really only a Linux distro abstraction. It will be useless for Windows, for example. Functions which you'd expect to be different on a non-RH distro should live in

The following patches are where I'm currently at with ESX support. I can now import a domain from ESX along with its storage. Note that I'm not yet doing any conversion. In fact, I've never even tested past the import stage (I just had an exit in there). The meat is really in the 4th patch. The rename of MetadataReader->Connection was because the Connection is now really providing

With this patchset I have successfully[1] imported a RHEL 5 guest directly from ESX with the following command line: virt-v2v -ic 'esx://yellow.marston/?no_verify=1' -op transfer RHEL5-64 Login details are stored in ~/.netrc Note that this is the only guest I've tested against. I haven't for example, checked that I haven't broken Xen imports. Matt [1] With the exception of

These 2 patches are mostly code motion. They were prompted by an apparent augeas error in BZ 613967 which didn't display useful error message. The error seems to happen in Converter::Linux. GuestOS::RedHat had a handy function which displayed verbose augeas error messages. This function moves into the new module where it can be used by both modules. The second patch is an consequential tidy

hi: I am on Mac OSX 10.4 using locomotive. My ActionMailer configuration is ActionMailer::Base.delivery_method = :smtp # or :sendmail or test ActionMailer::Base.server_settings = { :address => "mail.albertafilmworks.com", :port => 25, :domain => "brucebalmercanada.com" } ActionMailer::Base.perform_deliveries = true

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

The ioreadX() helpers have inconsistent interface. On some architectures void *__iomem address argument is a pointer to const, on some not. Implementations of ioreadX() do not modify the memory under the address so they can be converted to a "const" version for const-safety and consistency among architectures. Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> ---

On Wed, 8 Jan 2020 at 09:13, Geert Uytterhoeven <geert at linux-m68k.org> wrote: > > Hi Krzysztof, > > On Wed, Jan 8, 2020 at 9:07 AM Geert Uytterhoeven <geert at linux-m68k.org> wrote: > > On Tue, Jan 7, 2020 at 5:53 PM Krzysztof Kozlowski <krzk at kernel.org> wrote: > > > The ioread8/16/32() and others have inconsistent interface among the > >