Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2846C181F0 for ; Wed, 10 Feb 2016 09:48:46 +0000 (UTC) Received: (qmail 32413 invoked by uid 500); 10 Feb 2016 09:48:45 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 32357 invoked by uid 500); 10 Feb 2016 09:48:45 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 32346 invoked by uid 99); 10 Feb 2016 09:48:45 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Feb 2016 09:48:45 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 519F4E020E; Wed, 10 Feb 2016 09:48:45 +0000 (UTC) From: ntavares To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: 4.8.0 fix i18n es Content-Type: text/plain Message-Id: <20160210094845.519F4E020E@git1-us-west.apache.org> Date: Wed, 10 Feb 2016 09:48:45 +0000 (UTC) Github user ntavares commented on the pull request: https://github.com/apache/cloudstack/pull/1407#issuecomment-182282200 @Daan, yes the capitalizations are wrong in several places.... I've fixed the most visible (home page), but that's another matter. As for the double encoding, there were only two strings missing which include a upside-down question mark. Spanish use that a lot :) I've fixed these also on the PR. -NT -- -- Nuno Tavares --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---