| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Removed the gevolution plugin. It's barely supported and does some stuff we don't want to allow anymore.
Testing Done:
Compile test only
Reviewed at https://reviews.imfreedom.org/r/160/
|
| |
|
| |
|
| |
|
|
|
|
| |
Following the instructions at https://developer.pidgin.im/wiki/ReleaseProcess
|
|
|
|
| |
Obtained using the instructions at https://developer.pidgin.im/wiki/ReleaseProcess
|
|
|
|
|
| |
Specifically I ran this:
XGETTEXT_ARGS=--no-location intltool-update --report
|
| |
|
| |
|
| |
|
|
|
|
| |
should be done at least every release.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QuLogic: so, canceled or cancelled? that patch on #12130 is pretty thorough...
wabz: cancelled :D
wabz: that cancelled thing actually bothered me in the past
wabz: never quite enough to do such a patch :p
elb: that's an en_US vs en_GB thing
elb: both are correct, but canceled is more common in en_{US,CA} and cancelled in en_{GB,AU,NZ,etc.}
elb: personally, I use cancelled
QuLogic: yea, that's what I went for before, but I think I couldn't change any strings because we were frozen
QuLogic: you all had to pick the spelling that was opposite from the guy's patch, didn't you...
rekkanoryo: well, considering we're generally en_US in our strings, it should be canceled in our source
elb: considering they're both correct, and while I'm anal retentive, I'm not anal retentive about that, I have no preference ;-)
rekkanoryo: I don't really care either way, I just think that we should be consistently en_US or en_GB throughout
elb: right
elb: my point is, they're both correct for en_US
elb: one 'l' is simply more common
rekkanoryo: ah
rekkanoryo: if they're both technically correct for en_US, then "cancelled" is my vote
rekkanoryo: one 'l' always looks wrong to me
elb: the dictionary claims they are
Sorry, dwc.
Closes #12130.
|
|
|
|
| |
cron job doesn't work so hard.
|
|
|
|
| |
so hard every day.
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes #11399, #11447, #11454, #11491, #11506, #11543.
|
| |
|
|
|
|
|
|
| |
I fixed one issue in the Kannada translation (line numbers in the committed file, not original):
ENTRY: (kn.po, line 7201)
*** Format number mismatch for %s [msgstr:2] (there was an extra format)
|
| |
|
| |
|
|
|
|
| |
(I just runs our po/stats.pl script)
|
|
|
|
|
| |
and it really does make a difference on how long it takes the
nightly stats script to run
|
|
|
|
| |
work to do
|
| |
|
| |
|
|
|
|
| |
the po directory. This diff is entirely too large, I think.
|
|
|
|
| |
less work to do
|
|
|
|
|
| |
It's good to do this occassionally because it REALLY
speeds up the amount of time it takes stats.pl to run.
|
|
|
|
|
| |
but here it is. For reference, Google and Yahoo call it "email" and
dropping the hyphen on no-longer-new words is apparently standard practice.
|
|
|
|
| |
software.
|
| |
|
|
|
|
| |
strings back into use, now that we've gone back in time.
|
|
|
|
| |
through 71a27720e49364f4f24fc09309442fc3a2c17bc9
|
| |
|
| |
|
| |
|
|
|
|
| |
some translation updates. I have questions about gu.po, if someone sees that answered, we might need to revert that part of the change. It is all very confusing. The same person submitted the original gu.po and this update, but he called it gu_IN this time?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Way more changes that I initially thought I was going to make. I apologize
for the commit message spam. These changes bring a lot of consistency to
our capitalization and punctuation, especially of words like "e-mail".
For reference, I've used these rules (after discussing in #gaim):
e-mail, a case of two words joined:
"e-mail" - in the middle of a sentence caps context
"E-mail" - start of text in a sentence caps context
"E-Mail" - in a header (title) caps context
re-enable, a single word, would be:
"re-enable", "Re-enable", and "Re-enable" (respectively)
The reason this changeset exploded is that, as I went through and verified
these changes, I realized we were using improper capitalization (e.g. header
instead of sentence) in a number of dialogs. I fixed a number of these
cases before, and this corrects another pile.
This looks like I've made a LOT of work for the translators, but the impact
is significantly mitigated by three factors: 1) Many of these changes use
strings that already exist, or change one string in many places. 2) I've
used sed to correct the .po files where possible. 3) The actual changes
are extremely trivial.
|
|
|
|
|
|
|
|
|
|
|
| |
SF Patch #1353932 from resiak--
"In the blist's Tools menu, both Plugins and View System
Log had L as the mnemonic. This patch changes Plugins
to use G instead, and updates the translations
appropriately."
committer: Richard Laager <rlaager@pidgin.im>
|
|
|
|
|
| |
(16:18:11) rlaager: LSchiere2: make[2]: *** No rule to make target
`el.po', needed by `el.gmo'. Stop.
|
|
|
|
|
|
|
|
| |
I ran make dist, found lots and lots of changes. So I decided to clean
out the translations tracker as well. oh and we now have a greek
translation. there was also a kurdish translation, but that didn't tell
me everything I need to know to commit it (such as two letter language
code)
|
|
|
|
|
| |
I feel like committing make dist'ed po files is a good thing at this
point in time
|
|
sync the translations over from oldstatus so that I'm sure I'm not missing
anything, and since the oldstatus ones are at worst newer than the current
set of head ones.
|