keeleysam / audacity Goto Github PK

I translated some strings

Edit Labels: "start/end times display as zero" fix breaks screen reading
ability.

LL: I've seen some really strange (attempted) recoveries. I haven't yet
looked into them, but I shall soon since my wife is complaining about it as
well.

GA: These known problems have been reported. They should be verified and
escalated to P2 if valid:
 o If a crash occurs with two tracks open, multiple projects are recovered
 o Recovery fails if a track is imported then another added after the
autosave interval
 o Complete recovery failures (empty projects) seen on single tracks which
are only generated tones.
 o (Mac) freeze on Intel Macs when starting recovery
 o (Mac) (Intel and PPC) "Junk after document" warnings then recovered
project is empty. See here and download here an example auto save file and
_data folder. 

small correction in line 45

This correction is sent by the last translator Miguel Anxo Bouzada 
<[email protected]>

changed the version to 2.0.3

Correggo 2 errori di battitura (seleizona -> seleziona)

* GA: Much of the time, 1.3.7 or later on Windows cannot be relied on to
import files exported with the explicit "AIFF (Apple) signed 16 bit PCM"
filter. Appears to affect exports from recorded data (at any Defauit Sample
Rate), or from tones generated at 24-bit. Same problem occurs with the AIFF
24-bit option accessed with "Options" button, but not apparently the
comparable 16-bit option. Export Multiple seems affected the same way as
regular export. Tested at 44100 Hz, reading directly. On Mac, a user 22
March 09 reports 1.3.7 "suddenly" producing noise when importing AIFF files
where it did not before in many similar imports - user changed default
sample format to 24-bit at about the same time. More details here.

 * LL: Gale, have you been able to find a pattern to recreate this? I've
tried numerous variations on OSX and Windows and it always seems to import ok.

 * GA: Are you using a release build? In ANSI Release from HEAD, I created
a chirp tone in 24-bit quality, recorded it using stereo mix then exported
only the recorded track using the explicit (no options available) AIFF
(Apple) signed 16-bit PCM choice. I changed Quality to 32-bit, closed the
tracks and repeated the generation, record and export. I am not getting
noise on importing the files back into Audacity but what I can replicate is
that about half the time the files will crash both HEAD and 1.3.7 Unicode
Release; if they don't crash they import properly. So behaviour compared to
when I last tested is not the same. I have tried importing with the "All
supported files" and "FFmpeg-compatible files" filter and the problem is
identical. In 1.2.6 I can import these files dozens of times without problem. 

fixed wrong translations.

GA: There are reports every week of users losing data correctly reopening a
1.3 .aup file in the exact same 1.3 version they created it in. "Orphaned"
or "missing" blockfile errors are received and when users accept the
"recommended" course to delete, the project is silenced. This frequency of
data loss is not acceptable in 1.4.0. We should be on the alert for these
issues, and as soon as steps to reproduce are found, escalate the specific
problem to P2. One definite scenario where this has been reported is having
multiple projects open, and blockfiles are saved to the wrong _data folder.
GA has not yet managed to replicate it, though still has some more reported
steps to try and do so... 

(Windows Vista, 7)

GA: A significant problem for support workers. On some systems, running
Audacity in compatibility mode for XP seems to make the inputs appear in
Mixer Toolbar and work/be selectable. Best solution could be to integrate
Device Toolbar into Mixer Toolbar, making sources appear as separate
devices for all Windows versions, with the sliders above the respective
dropdown. Cheaper short-term solution may be to turn Device Toolbar back on
as it is. See proposal.

ajustes

New translations in ru

Úprava překladu

I added some translations into Belarusian and corrected the previous 
translations

I'm Melih Aktas, the first Turkish translator both Audacity and the website of 
Audacity. I was not able to contribute to Audacity project for many years 
because of my university education. Now, I add a translation that prepared from 
scratch. I will continue to develop this translation in future.

GA: Not reproducible to order, but likely to occur if repeatedly
duplicating short selections in a track. Discussion here.

GA: Reproducible scenario found if the short clip is time-shifted away from
zero and not at the current project rate. If tracks are mixed/rendered or
exported, audio in the short clip may be lost.

MJS: Leland has committed a fix for this 'reproducible scenario', confirmed
here (Win XP). How do we know if this has fixed the 'unreproducible scenario'?

GA: Confirmed the "reproducible" part of the bug is fixed for me on Ubuntu
and for another user on Fedora. However that user has led me to this
further reproducible scenario which seems to be an issue with loop play
when another track is not at the project rate. 

Itzulpen txiki bat proba gisa

GA: Leads to loss of association between boundaries and original audio, and
loss of audio if the clips were separated by white space. See this thread.

GA: Claimed by Vidyashankar Vellal 

I translated AboutDialog cpp: 162, 197, 201

a mistake fixed: "primai" > "prima"

Translated a little bit.

Mistranslated string

Just google Erro 2116

Identify directory shell(Linux).

Correct translation of "recent files"

GA: 19 Sep 09 - Very frequent reports on Windows, occasional on Linux.
Usually affects only re-opened projects. No known scenario to reproduce,
though select all, copy/paste to new project and save that project always
cures it.

MJS: Reproducible error when project includes silence confirmed as 'fixed'
on Win by GA after LL's fixing.

GA: Forum and other complainants invited to try Nightly build to see if
errors still occur. 

* add the accent on the "a" of "À propos"
* add a space between a word and a "!"
* add a space between a word and a "?"
* add a space between a word and a ":"

[deleted issue]

GA: Import a file, place cursor in centre and zoom in four or five times.
Then play a few seconds of audio so that the cursor goes past the scroll.
Press Space and the timeline remains where stopped (maybe OK). Press Space
again and playback restarts from original point but that is now at far left
of scroll, not in the middle. The context preceding that playback position
is now lost, requiring a fiddly drag back on the horizontal scrollbar, or a
zoom out and back in. Or, you must draw a selection region when you may not
want to do so. Very irritating for repeated zoomed-in editing at one spot.

JC: This is a P4, or better still a feature request for improved
scrolling/zooming behaviour. Let's get some detailed usability enhancements
written up for a GSoC 2010 idea? Then drop this as a P2. In this area I'd
see 'zoom to selection' should be 90% not 100% zoom, so that we get
context, plus also option for smooth scroll on sufficiently fast machines.
Can we replace this P2 with a detailed/motivated feature request?

GA: Need time to consider exactly what may or may not be a feature request,
however I and several others regard the subject issue as excessively
disruptive to "repeat editing" workflow, and completely unacceptable. I've
sometimes actually exported WAV and used other editors in order to be free
of it. 

Corrected double spacing
Corrette doppie spaziature

Symptoms:

 * Achieved recorded level only matches level indicated on the Recording VU
meter if the Audacity input slider is at 100%. (DB finds similar behaviour
on XP with Logitech USB microphone, but GA can't reproduce with USB
external sound cards).

 * (DB finds this only on Vista) Launch Audacity > Record > Stop > adjust
the system input level > Record again; or Launch > adjust system input
level > Record resets system level to that before the adjustment, unless
monitoring is on. Please test with both motherboard and external USB
devices. Adjusting system slider is necessary if it happens to be set above
clipping level because lowering the Audacity slider only scales down the
clipped signal instead of lowering the system slider. Especially confusing
for VI users. 

GA: SBSMS now fixed by DH, leaving the subject problem. See this thread.

DH: Nyquist will probably need further discussion (was mentioned in the
original 'white space' thread I believe) - really processing clips
separately could produce artefacts... possible solutions include:

 o simply running 'detach at silences' after the effect (I haven't looked
at how this works yet but it seems hopeful)
 o changing the nyquist interface (e.g. the 'nil means white space' option)
which would involve changing all of those plug-ins
 o recognising the known plug-ins by filename and dealing with them
appropriately (pretty unpleasant temporary solution) 

GA: I always recommend complainants to detach at silences but it won't work
at 16-bit quality because the effect will add dither noise. The only P2
part of this is to stop the clip boundaries being removed. Longer term I'm
still getting the impression having absolute silence between clips rather
than white space would solve a lot of issues. 

nicht Ton, sondern Tonspur oder Audio. 
#: src/Menus.cpp:404
msgid "&Export Audio..."
msgstr "Tonspur &exportieren …"

#: src/Menus.cpp:409
msgid "Expo&rt Selected Audio..."
msgstr "Ausgewähltes Audio expo&rtieren …"

Typo in french translation

[deleted issue]

GA: Reported several times on Windows. See this thread. 

Just changed a little casus misstake

- Various correction
- Additions for some non-translated stuff

PATCH: So FFMPEG can export ma4 format at 48KHz

I'm really doing this to see what google code tracker looks like when used
as a patch tracker.

GA: When a saved project is re-opened it fails with "duplicate attribute"
error. Almost always involves imported MP3s; the .aup file shows one or
more tags with two "name" attributes, for example <tag name="ARTIST"
name="ARTIST"/>. Changing second "name" to "value" allows project to
re-open. GA (Windows) and a Mac tester have tried to reproduce this with an
MP3 that created this issue for one user, but the projects re-opened
perfectly. Bug also reported to occur if a diacritic is included in a label.

GA: One report from CVS on Mac 06 July 09 finds a project with diacritics
in labels that saved in 1.3.7 with duplicate attributes saves correctly in
CVS. 

* add a space between "à cette" and "adresse"

GA: To reproduce: 

 1. Turn linking on, create 30 seconds default tone, select 5 - 10 seconds
and Amplify by -20 dB to see it

 2. Place label at 15 seconds, select 3 - 12 seconds and Effect > Sliding
Time Scale (20% start and end tempo change), or Change Speed or Change
Tempo (20% change)

 3. Label does not move. Labels do move with Repeat in the above scenario,
and do move with Reverse if label included in selection region. 

RA: If a single track is being processed by the Truncate Silence effect,
the linked label track is not changed to match. This should be simple to
fix for the case where there is only one audio track and the associated
label track. This bug does not cover the case where there are multiple
audio tracks selected for truncation - that is a much lower priority bug.

 * To illustrate, generate a 30 seconds DTMF sequence
 * Add labels to some visually obvious places on the waveform
 * Select the audio, and Truncate Silence
 * Notice the labels haven't moved, when they should have. 

small changes

GA: Fixable by user changing compatibility mode to Vista SP2 or XP SP3.
Reports where this error occurs say Audacity installs without
compatibility, but that isn't in itself a condition to reproduce it.

GA: When applied over existing split lines, these effects sometimes produce
a faint or no clip line. This may be demoted, subject to discussion. See
this thread. 

GA: Experienced on Windows XP in one project that crashed regularly on
separate days but now won't do so, also several similar anecdotal reports.
There is also an implication that Noise Removal is more likely than other
effects to trigger the problem. JC suggested and was agreed we should aim
to do stress-testing with small block sizes to try and force the problems
to occur and (later added) that we should use the scripting feature to do
this (improving our chances that we can repeat the problem) .

JC: A label issue? (I have not seen this crash yet).

GA: Without labels in my case, with in others, so believed that labels not
relevant. 

[deleted issue]

Just a test with a few strings. More coming soon.