Skip to content
Projeler
Gruplar
Parçacıklar
Yardım
Yükleniyor...
Oturum aç / Kaydol
Gezinmeyi değiştir
C
core
Proje
Proje
Ayrıntılar
Etkinlik
Cycle Analytics
Depo (repository)
Depo (repository)
Dosyalar
Kayıtlar (commit)
Dallar (branch)
Etiketler
Katkıda bulunanlar
Grafik
Karşılaştır
Grafikler
Konular (issue)
0
Konular (issue)
0
Liste
Pano
Etiketler
Kilometre Taşları
Birleştirme (merge) Talepleri
0
Birleştirme (merge) Talepleri
0
CI / CD
CI / CD
İş akışları (pipeline)
İşler
Zamanlamalar
Grafikler
Paketler
Paketler
Wiki
Wiki
Parçacıklar
Parçacıklar
Üyeler
Üyeler
Collapse sidebar
Close sidebar
Etkinlik
Grafik
Grafikler
Yeni bir konu (issue) oluştur
İşler
Kayıtlar (commit)
Konu (issue) Panoları
Kenar çubuğunu aç
LibreOffice
core
Commits
07202af3
Kaydet (Commit)
07202af3
authored
May 31, 2012
tarafından
Korrawit Pruegsanusak
Dosyalara gözat
Seçenekler
Dosyalara Gözat
İndir
Eposta Yamaları
Sade Fark
fix some typo
Change-Id: Ib88169968d164c88703505da022887ea8d53c721
üst
efecdece
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
5 additions
and
5 deletions
+5
-5
README
i18npool/source/breakiterator/data/README
+3
-3
README
sw/qa/extras/README
+1
-1
README
tail_build/README
+1
-1
No files found.
i18npool/source/breakiterator/data/README
Dosyayı görüntüle @
07202af3
...
...
@@ -2,11 +2,11 @@ The originals of these come from svn checkout
http://source.icu-project.org/repos/icu/icu/trunk/source/data/brkitr they no
longer appear in the icu tarballs, but are in icu's svn
At various stages these copies have been customized and are no
t
horribly out of
At various stages these copies have been customized and are no
w
horribly out of
sync. It unclear which diffs from the base versions are deliberate and which
are now accidental :-(
We need to review the various issues referenced in the commits that caused
cust
i
mizations and see if they're still relevant or not, write regression tests
for them, if any are still rel
a
vant then apply the changes back on top of the
cust
o
mizations and see if they're still relevant or not, write regression tests
for them, if any are still rel
e
vant then apply the changes back on top of the
latest versions.
sw/qa/extras/README
Dosyayı görüntüle @
07202af3
...
...
@@ -123,7 +123,7 @@ similarly to the property you want (getXYZ()). If there is none, it is most
probably a property that can be read using XPropertySet:
uno::Reference<beans::XPropertySet> properties(textDocument, uno::UNO_QUERY);
sal_Int32 val
ue
; // the right type for the property
sal_Int32 val; // the right type for the property
properties->getPropertyValue("CharacterCount") >>= val;
If there is a function to obtain the property, you need access it using the right interface.
...
...
tail_build/README
Dosyayı görüntüle @
07202af3
...
...
@@ -5,7 +5,7 @@ A few module that normally get built at the end of the build process
are already converted. this 'pseudo-module' build them all as one.
As module get converted to gbuild they can be added to this module
if they fix the nece
e
sary pre-requisite. that is:
if they fix the nece
s
sary pre-requisite. that is:
To qualify a module must not be the dependant of any other module,
except postprocess or if the other module itself is under tail_build
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment