不要臉的，你不要找到機會就打我，去找你那些賤人和妓女，只有那些賤人、妓女、越南下等货才配……和你才能配對做狗男女……有做就要敢當，若有 下等貨
要你，你就要趕快去，我會祝福趕你快和其中的 賤人、妓女、下等貨 配對，不用擔心我，我命好，沒在你身邊我只會越來越好……
你那些賤貨，天生下來就是賤，天天要给不同人幹……說真的那些賤人、妓女、越南下等貨 真的很試合你……而你也只配和這種下三爛的貨色配對做狗男女……
我和你常吵架是因為我們層次不同，所以無法好好相處，你只配那下等貨……
On Mar 9, 2020, at 04:42, Han-Wen Nienhuys wrote:
>
> On Mon, Mar 9, 2020 at 12:44 AM Dan Eble wrote:
>> I agree that lots of duplication is something that should be avoided, but so
>> is the conflation of style and meaning. A lyric hyphen separates syllables;
>> this arrow thing means
https://codereview.appspot.com/553620043/diff/581760043/scripts/musicxml2ly.py
File scripts/musicxml2ly.py (right):
https://codereview.appspot.com/553620043/diff/581760043/scripts/musicxml2ly.py#newcode2287
scripts/musicxml2ly.py:2287: if n._measure_position == Rational(0) and n
!=
Francisco Vila writes:
> El 9/3/20 a las 21:19, Han-Wen Nienhuys escribió:
>> On Mon, Mar 9, 2020 at 9:07 PM Francisco Vila wrote:
> Sorry if it's in CG already, I could be wrong, but Doc build is not
> multi-thread safe, first time at least. It uses files generated by the
> build
El 9/3/20 a las 21:19, Han-Wen Nienhuys escribió:
On Mon, Mar 9, 2020 at 9:07 PM Francisco Vila wrote:
Sorry if it's in CG already, I could be wrong, but Doc build is not
multi-thread safe, first time at least. It uses files generated by the
build process itself.
Right?
well, the doc build
On Mon, Mar 9, 2020 at 9:07 PM Francisco Vila wrote:
> >> Sorry if it's in CG already, I could be wrong, but Doc build is not
> >> multi-thread safe, first time at least. It uses files generated by the
> >> build process itself.
> >>
> >> Right?
well, the doc build uses lilypond, which is
El 9/3/20 a las 20:41, David Kastrup escribió:
Francisco Vila writes:
Sorry if it's in CG already, I could be wrong, but Doc build is not
multi-thread safe, first time at least. It uses files generated by the
build process itself.
Right?
I tend to do
make clean test-clean doc-clean
El 9/3/20 a las 20:37, David Kastrup escribió:
Jean-Charles Malahieude writes:
Le 09/03/2020 à 18:21, Francisco Vila a écrit :
Anyway. I expected wrongly to see translated es/changes showing
online, but this will only happpen when the second stable minor
version occurrs. Right?
Wrong!
Francisco Vila writes:
> Sorry if it's in CG already, I could be wrong, but Doc build is not
> multi-thread safe, first time at least. It uses files generated by the
> build process itself.
>
> Right?
I tend to do
make clean test-clean doc-clean
CPU_COUNT=9 make -j9 && CPU_COUNT=9 make -j9
Jean-Charles Malahieude writes:
> Le 09/03/2020 à 18:21, Francisco Vila a écrit :
>> Anyway. I expected wrongly to see translated es/changes showing
>> online, but this will only happpen when the second stable minor
>> version occurrs. Right?
>>
>
> Wrong! translation has to be merged into
Hi,
Another problem with switching to Python 3:
cd Documentation && make translation status
crashes on branch translation (after merging master into it); it works
well as expected on transaltion-staging (still on Python 2).
the message is
-*- mode: compilation; default-directory:
Le 09/03/2020 à 19:09, David Kastrup a écrit :
Francisco Vila writes:
El 9/3/20 a las 11:58, David Kastrup escribió:
I think I was told to run the update script and forgot. I am not sure
where to run it now in order to get the results somewhere.
do
make translation-status
from
Francisco Vila writes:
> El 9/3/20 a las 11:58, David Kastrup escribió:
>> I think I was told to run the update script and forgot. I am not sure
>> where to run it now in order to get the results somewhere.
>
> do
>
> make translation-status
>
> from Documentation/ .
>
> Then commit changes
Sorry if it's in CG already, I could be wrong, but Doc build is not
multi-thread safe, first time at least. It uses files generated by the
build process itself.
Right?
--
Francisco Vila, Ph.D. - Badajoz (Spain)
paconet.org , lilypond.es
El 9/3/20 a las 11:58, David Kastrup escribió:
I think I was told to run the update script and forgot. I am not sure
where to run it now in order to get the results somewhere.
do
make translation-status
from Documentation/ .
Then commit changes to
El 9/3/20 a las 10:35, Valentin Villenave escribió:
I’m a bit uncomfortable with the hardcoded date in translations.itexi:-)
translations.itexi is not meant to be manually edited; it is a generated
file.
I agree it _looks_ harcoded because it's old now.
--
Francisco Vila, Ph.D. - Badajoz
Le 09/03/2020 à 18:21, Francisco Vila a écrit :
Anyway. I expected wrongly to see translated es/changes showing
online, but this will only happpen when the second stable minor
version occurrs. Right?
Wrong! translation has to be merged into master and then the website
regenerated.
And I'm
El 8/3/20 a las 21:04, David Kastrup escribió:
In the translations, the links need to get redirected to
language-specific versions. Depending on the language, Partly this
happens by changing the macros creating the documentation links (I think
that should likely be the most sensible way),
Yep.
http://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=ed1c70f3a7704253cf93c5c031d6f9ce5408f26c
--
Phil Holmes
- Original Message -
From:
To: "Trevor" ; "Lily-Devel List"
Sent: Monday, March 09, 2020 1:49 PM
Subject: Re: Missing link
Hello
On 01/03/2020 23:10, Trevor
Hello
On 01/03/2020 23:10, Trevor wrote:
Congratulations to all involved in getting 2.20 out the door!
This is a big step forward.
One minor glitch I noticed: in http://lilypond.org/website/all.html
the link to the 2.18 documentation in the list of previous stable
versions
has gone AWOL,
Valentin Villenave writes:
> On 3/9/20, David Kastrup wrote:
>> I think I was told to run the update script and forgot. I am not sure
>> where to run it now in order to get the results somewhere.
>
> Oh, good. Perhaps we should mention it in the CG’s release-work.itexi
> to make it less easy
On 3/9/20, David Kastrup wrote:
> I think I was told to run the update script and forgot. I am not sure
> where to run it now in order to get the results somewhere.
Oh, good. Perhaps we should mention it in the CG’s release-work.itexi
to make it less easy for people to overlook in the future?
Valentin Villenave writes:
> On 3/8/20, Francisco Vila wrote:
>> Yes please, it was painful to re-organize a half-translated version. Now
>> is soon enough, still.
>
> By the way (on a more-than-slightly unrelated note), how up-to-date is
> the official translation status page?
>
On 3/8/20, Francisco Vila wrote:
> Yes please, it was painful to re-organize a half-translated version. Now
> is soon enough, still.
By the way (on a more-than-slightly unrelated note), how up-to-date is
the official translation status page?
http://lilypond.org/translated.html
I’m a bit
On Mon, Mar 9, 2020 at 12:44 AM Dan Eble wrote:
> I agree that lots of duplication is something that should be avoided, but so
> is the conflation of style and meaning. A lyric hyphen separates syllables;
> this arrow thing means something more.
Can you have a hyphen and a transition between
On Sun, Mar 8, 2020 at 11:56 PM Karl Berry wrote:
>
> Hi Han-Wen - neither fmt generation nor any other runtime generation has
> ever been parallel-safe. Even if I added locking to mktexfmt (I guess
> you are making use of the dynamic fmt creation), something I am not at
> all anxious to do, the
Hello,
Here is the current patch countdown list. The next countdown will be on
March 11th
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
***
Push:
5820 Add some const declarations to page breaking code -
27 matches
Mail list logo
