> [...], we can definitely use 8 bit output to represent SDF and
> render acceptable text using it. Now, we can either eliminate the
> current 16 bit output, or, we can keep both 16 and 8 bit output.
> What do you think will be the better option? I think we should keep
> a single output (probab
Dominik,
> With your agreement — and I am happy to hear feedback and answer
> questions — I would like to start upstreaming our implementation of
> COLRv1 support into FreeType. This contribution is meant as an
> addition to the current experimental support of COLRv0.
I've just pushed a branch
> rm -rf builddir && mkdir builddir && cd builddir
> meson .. \
> --prefix=$3 \
> --libdir=lib \
> --buildtype=release \
> --strip \
> --cross-file ../cross_toolchain.txt \
> --default-library shared \
> -Dharfbuzz=disabled > ../../config.log 2>&1
I tried
> no test is done line 270, especially :
>
> ftoption_command += ['--enable=FT_CONFIG_OPTION_USE_HARFBUZZ']
>
> is set unconditionally
Oh, you are using the latest tarball for building FreeType! I have
missed that, sorry. Please use the git repository, which has this
Meson problem already fi
> Please see ftoption_unset in builds/unix/configure.raw. This is how
> a robust build system should handle this. Our Cmake and meson
> scripts need to mature a bit to handle ftoption.h that was altered
> by whatever winds or failed builds.
As mentioned in another mail, this Meson support bug h
>> Oh, you are using the latest tarball for building FreeType! I have
>> missed that, sorry. Please use the git repository, which has this
>> Meson problem already fixed (and which I used for testing your
>> case).
>
> Don't you think that a bug in the build system is worthy of a new
> minor re
>> [...] Can't run git master anymore :(
>>
>
> If I had to guess it's probably that FT_PIXEL_MODE_GRAY16 was added
> to the middle of the enum, changing the values of the later
> enumerators, changing the ABI.
Ouch. Fixed in git, please try! And thanks for the report and
analysis.
Wern
Alexei,
> + * builds/toplevel.mk: Place `FTMODULE_H' in include/.
Have you tested this commit on a Unix box with a build where 'srcdir'
!= 'builddir', and where 'srcdir' is read-only? My gut feeling says
that your commit is not correct.
We have the following rules, which I consider the ri
>> In other words, this change
>>
>> -INCLUDES := $(subst /,$(COMPILER_SEP),$(OBJ_DIR) \
>> - $(DEVEL_DIR) \
>> +INCLUDES := $(subst /,$(COMPILER_SEP),$(DEVEL_DIR) \
>> $(BUILD_DIR) \
>>
[A preliminary remark: We have to improve FreeType's terminology. For
example, in `ftconfig.h` there is some talk about 'build directory'.
Users might assume that this refers to the directory where
compilation puts its object files. However, this is not the case. I
will probably do `s/BUIL
> [A preliminary remark: We have to improve FreeType's terminology. For
> example, in `ftconfig.h` there is some talk about 'build directory'.
> Users might assume that this refers to the directory where
> compilation puts its object files. However, this is not the case. I
> will probably
> What is the status of the test framework project?
Dormant.
> It was attempted during GSoC 2020 but the submitted code does not
> satisfy one of the design criteria: just work. Several parts of the
> project can be improved.
I fully agree. Collaboration with the student was difficult,
unfor
Hello Greg,
thanks for chiming in!
> Running continuous integration on Savannah isn't really an option.
Yes.
> If the project moves to gitlab as was discussed months ago. I would
> not be opposed to porting my azure configs to gitlab ones.
Hopefully, this is done soon. Anurag?
> However
> I will try to make a PR once you have migrated to gitlab or
> elsewhere.
Great!
> but until then I'd rather not waste the effort until you've
> committed to a more modern git interface.
I fully agree.
Thanks for your offer!
Werner
> I took some notes on what formatting details I need to pay attention
> to in the future (in particular with regards to argument lists,
> double spaces after types and between doc sentences, use of tilde in
> docs, and I took some hints on how to phrase commit messages with
> regards to distinct
>> Running continuous integration on Savannah isn't really an option.
>
> The regression server can poll Savannah every 10 minutes. [...]
Due to our move to freeedesktop.org (hopefully really soon) this
is no longer a problem.
>> However it is not really practical for me to set up servers for
>
> The proposed patch looks like this
> https://github.com/drott/freetype2-colr/commit/a4c2f36b1f6a7a6799248d7e13745f290fa24a69
>
> This would only be needed as long as the feature is not officially
> released, since then we could use version check macros to achieve
> the same.
>
> What do you t
Dominik,
I've just merged the 'colr' branch to master (with some minor tweaks
as discussed) and pushed it to the FreeType git repository at
https://gitlab.freedesktop.org/freetype/freetype
Let's see whether mirroring to Savannah works as expected...
>> (1) How can your code be tested? It s
Folks,
this year GSoC is different in comparison to previous years: The
amount of time a student is going to work on a project has been
reduced by 50%. In other words, it's no longer 350h but only 175h.
As a consequence, projects must be down-sized to adjust to the
available time.
If you have
> using the latest harfbuzz version, I have this warning [...]
>
> ../src/autofit/afshaper.c:135:5: warning: 'hb_ot_tags_from_script' is
> deprecated: Use 'hb_ot_tags_from_script_and_language' instead
> [-Wdeprecated-declarations]
This is harmless but admittedly annoying. I didn't find the en
We are in the process of migrating FreeType's git repository and
infrastructure from Savannah to freedesktop.org.
https://gitlab.freedesktop.org/freetype/freetype
Savannah's git repository will become read-only for developers soon
but stay in sync with the new location as a mirror.
I've just
> Tested the new GitLab instance by doing
> https://gitlab.freedesktop.org/freetype/freetype/-/merge_requests/3
Thanks a lot!
> Next step: find out what it means for the code to not have a hard
> count of 2, as suggested in the HarfBuzz repo.
Mabe use a hard count of 3? AFAIK, only Indic scri
I've just imported the 'freetype2-demos' repository to
freedesktop.org. I used the opportunity to strip off the digit 2,
from the repository name, similar to what has been done for the
'freetype' repository.
https://gitlab.freedesktop.org/freetype/freetype-demos
Please no longer push to the S
I've just imported the 'freetype2-demos' repository to
freedesktop.org. I used the opportunity to strip off the digit 2,
similar to what has been done for the 'freetype' repository.
https://gitlab.freedesktop.org/freetype/freetype-demos
Please no longer use the Savannah repositories!
We
>> If you have suggestions and/or ideas for new GSoC projects that fit
>> into FreeType, please tell us! The list of projects can be found at
>>
>> https://www.freetype.org/gsoc.html
>
> finish VF driver ?
Idea re-added, thanks.
Werner
Alexei and others,
what do you think of moving the 'freetype-web' git repository
https://cgit.freedesktop.org/freetype/freetype-web/
to FreeType's gitlab group, too? The actual copying of its contents
to 'www.freetype.org' happens every 10 minutes with a small cron
script on my freedesktop
> (With GitLab's CI, you don't need a 10 minute cron an can instead
> make CI rsync every commit to master as it comes)
Well, never touch a running system :-) The mirroring stuff is many
years old, but I'm open to any improvements.
Werner
Hello Laurence,
> I wondered if you are able to benchmark timings for VF instance
> generation from FreeType. I’d like to know how far away my own
> Samsa JavaScript implementation is from FreeType C.
this is an interesting idea! The natural place to add such code is
FreeType's `ftbench` demo
> Google has published more info on this vulnerability now at:
> https://googleprojectzero.blogspot.com/p/rca-cve-2020-15999.html
Thanks!
Werner
Hello Justyna,
> Before flagging the font as 'tricky' you are checking its name and
> comparing it with the trick_names table defined in ttobjs.c file.
> This causes that some fonts which aren't tricky are also flagged and
> as a result we can't use autohinting on it.
What names are you talkin
> [Justyna] To be more precise, my case is PDLCJH+OCR-A font. This is
> incremental font build of OCR-A font.
The correct term is not 'incremental font' but 'subsetted font': The
PDF generator takes your input font and omits all glyphs not necessary
in the output file, thus creating a subset of
> What would be the process of attempting to add animation to fonts?
No chance IMHO. Given that you can have little animated GIFs and the
like embedded in a web page, I don't see any necessity for such a
feature. Please remember that fonts are intended primarily to be
printed.
> Here is a pub
> [smooth] Reduce copying during integration phase.
>
> We now record `cover' and `area' directly into the linked
> list. This makes rendering faster by 10% or even more at larger
> sizes.
Very nice :-)
Werner
Hello Giorgos!
> I would like to contribute to one of your GSoc 2021 projects and
> more precisely in the "Improve FreeType demo programs" project. The
> last few days (from the organizations announcing) I look into the
> git-repo code and I am quite excited.
Great!
> I would like to ask you
Hallo Utkarsh!
> I am interested to participate as a student in Freetype
> organization. Can you please send me a sample to give you the
> proposal so that my proposal selected chances get higher.
It doesn't work like that. First of all, you have to select one of
the topics listed at
http
Hello Sarthak,
> I am interested to work on this year's GSoC Project - "Develop a
> test framework for checking Freetype's rendering output".
Great!
> So I have done some googling from my side and it helped me to make
> many things clear, I have also read some of last year commits and
> maili
Hello Manish,
> Want to join the community to discuss the further process with
> mentors and contribute towards the Projects for Google Summer of
> Code 2021.
>
> Looking forward to becoming part of the FreeType Community.
This sounds great, thanks. Please look up similar questions that have
Hello Utkarsh,
> I want to contribute in the topic Add a ‘capability database’ to
> FreeType's auto-hinter.
Great!
> I have understand what the problem demands. So can you please tell
> me to where I can find the API and source code for this problem? As
> I am not getting these.
What exactl
Hello Anshuman,
>> Also, Which git repository hosting device Freetype uses - Github or
>> GitLab?
This question deserves a special answer: Right now, please use the
gitlab instance on 'freedesktop.org' from which the FreeType
repository should be cloned.
https://gitlab.freedesktop.org/freety
> Is it necessary that project in this organization can be done only
> on Linux or window can also be used?
Both work.
> The source code can be completely cloned on windows?
Yes.
> As I am facing some problem in Windows, so please reply soon
Uh, oh, don't use the phrase “please reply soon”.
> As directed by you i have tried all the things and i think I have
> gathered some good amount of info,
OK.
> As far as CI part is concerned which was earlier not compatible with
> Savannah, but as whole codes moved to gitlab, now we have probably
> multiple ways to implement that, either we c
Hello Aman,
> I am interested in the project -_"Develop a test framework for
> checking Freetype's rendering output"
Great!
> 1. What signifies the meaning of word "font corpora" as i haven't
> found anything about by googling it.
A good and valid question.
'Corpora' is the plural form of t
> [...] for getting well in work with freetype i need to study whole
> documentation of freetype or i just need to have the intro and build
> it to the system,
Of course it's not necessary to read everything, but you should get a
feeling for the library, this is, actively play around with the co
Hello Sarthak,
thanks for your thoughtful e-mail. I think you've exactly hit the
problems.
> In the last few days, I have come across Freetype's Documentation
> and previous contributions on this project(GSoC), what I have
> observed is
>
> - Most of the things are already implemented in it,
>> > - There should be some custom test harness in concurrence with
>> > checks for more accurate results.
>>
>> What exactly do you mean with 'more accurate results'?
>
> I have used in context to check for compile errors more precisely.
I still don't get it, sorry. Please elaborate.
Wer
Hello Sarthak,
> I want suggestions regarding generating HTML pages depicting the
> comparison, as this project wants to add some good UI, or can say we
> need something more functional and reflexive than the current one.
I don't have suggestions, since I'm not acquainted with those issues.
Ac
Hello Ben,
> While investigating some odd behavior, I discovered that in FreeType
> if a TrueType glyf contains instructions which read/modify/write a
> CVT entry and the glyph is loaded more than once the modified values
> persist across calls. The persistence is in the (TT_SizeRec_)
> size.cv
Hello Aman,
> I have read archive on orgs. Mailing list. I have some doubts, as
> this year's GSoC time is reduced to half, which implies that project
> should be smaller, and what sarthak have stated in his earlier mail
> (four or five points), is quite tough to be completed in such a
> short
>> [...] Thanks to the similar GSoC project last year, there should
>> only be incremental improvements necessary and not the need to
>> start from scratch. As far as I can see, the migration of the CI
>> to the gitlab instance at freedesktop.org is 100 to 200 lines of
>> code, improving the UI i
Hello Manish,
> Through Community Platform, I meant a Full Stack Forum for the
> upcoming contributors or the Developers within where they can
> interact with each other.
Thanks for your offer, but no. The 'official' communication channels
for FreeType are intentionally e-mail only. Having o
> If he is ok with that we can do this type of thing it will be like
> doing different different subproject under same projects name, and
> no collaboration to be done like this as you have mentioned earlier.
I think the best solution is that you don't use the term 'subproject'
at all. Instead,
> Do share your remark over this or can I proceed according to what he
> have suggested or what, accordingly i will see the things, and the
> most ambiguous thing in current is - whether i have to make proposal
> for the entire thing, or just for the subproject he suggested me to
> do so.?
As dis
Hello Aman,
> i wanna ask that can we run this framework in any other way than
> running locally or not?
The idea is to have this run remotely eventually, using the CI
capabilities of the gitlab instance on freedesktop.org (or maybe
something else in case this isn't sufficient for whatever rea
Hello Moazin,
> I'm free for a few months and I'd like to finalize the OT-SVG
> project.
Excellent!
> [...] I'm wondering what approach would let applications/libraries
> benefit the most from FreeType's OT-SVG support.
I think the main benefit is simplifying the interface, this is,
letting
> inside test-font.sh, there is a function written
> xvfbRunAndScreenShot, it will show error and only blank png's will
> be generated, as far as there is no ../freetype2-demos/bin/ftgrid
> directory found in our demos program, and there is no branch in
> demos for GSoC's Gregs works. It will on
>> It is not clear what problems arise for you because of the local
>> vs. remote thing. Please elaborate. Maybe I don't understand you
>> correctly.
>
> When I am trying to run it locally it simply generates blank html
> report of the comparison and blank images, i am doing everything
> what
> but still confused over the thing that whether we have to follow the
> traditional method all the time i.e. xvfbRunAndScreenShot, and check
> some enhancement in it itself, or we have to do it manually all the
> time or student need to figure it out by themselves a suitable
> substitute of it?
> I mean to say that as Alexei have suggested us to run it directly,
> by not using Xvfb and capturing the screenshot by pressing simply
> [P], that is giving us the .png file saved in same directory. I
> think this is what you use to test it in a manual way.
Ah, ok, understood. Of course, this
Hello Aman,
> I have a query that can we know the statistics of FreeType's GSoC,
> in simple words can we know that how many students have submitted
> their proposal and for what what project somewhere, or this
> information will be anonymous till the results will announced.
sorry, but this is
Hello Ozkan,
> Current freetype2.m4 has 'dnl'ed notes about not quoting AS_HELP_STRING
> since 2003. Here are the issues:
>
> - The dnl notes prepend 5 spaces of unwanted indentation to help
> string
Thanks for the report, I've fixed it.
> - There are no apparent reasons to not quote thos
Hello Alexei,
> During my memory management review, I noticed
> ft_lzwstate_stack_grow. It seems to drop stack_0 when relocating to
> the heap memory without copying it. How is this even supposed to
> work? Would you please take a look at this function?
Good question. My knowledge of LZW s
>> > Is relocation ever triggered while uncompressing fonts? If yes,
>> > is the corresponding font correctly read and displayed?
>
> Oh yesss!
> $ bin/ftview 44 ../hanglg16.pcf.Z
> pcf_get_metrics: invalid metrics for glyph 2081
> pcf_get_metrics: invalid metrics for glyph 2082
> pcf_get_metri
>> > Oh yesss!
>> > $ bin/ftview 44 ../hanglg16.pcf.Z
>> > pcf_get_metrics: invalid metrics for glyph 2081
>> > pcf_get_metrics: invalid metrics for glyph 2082
>> > pcf_get_metrics: invalid metrics for glyph 2083
>> > ...
>> >
>> > $ bin/ftview 44 ../hanglg16.pcf
>> > is clean as a whistle!
>>
>> I
Hello Alexei,
> You used to release a new version around this time of year. What are
> your plans this time around? Are you waiting for some official
> specs for COLRv1?
Not really for the official specs, but for green light that the COLRv1
stuff is OK to be published as experimental but stab
> We have already discussed 8 Bit SDF earlier and I agree that 8 Bits
> is enough for producing acceptable interpolation for rendering. Here
> is the mail for your reference:
> https://lists.nongnu.org/archive/html/freetype-devel/2020-12/msg00042.html
Thanks.
> Back then I was waiting for other
Hello Sarthak,
> I have recently received my GSoC selection mail. I would like to
> thank my mentor @Werner LEMBERG and other Freetype
> community members for their constant support and guidance.
>
> It will be my privilege to work with such a wonderful organization,
> wi
> While trying to generate MD5 hashes of rendered glyphs, I came across this
> discussion:
> https://lists.nongnu.org/archive/html/freetype-devel/2017-03/msg1.html
>
> I tried compiling freetype with FT_DEBUG_LEVEL_TRACE defined and set
> the env variable FT2_DEBUG to bitmap:3, but ftgrid do
> Apparently I forgot you could send files via email😅
This looks great, thanks! It's a good start.
>> It would be great if you could provide some feedback (what should I
>> add/remove/change etc), so that sarthak can then implement it (and
>> I can mentor him😂).
Alas, I can only answer this if
> Since you and Alexei agree on 8bit being enough: Please change to
> 8bit!
It seems that the patch hasn't been applied yet. Can we please go
forward so that it becomes part of the next release?
Werner
> I'm attaching the two patches below, [...]
Thanks for applying. I've polished the code a bit; please check.
Werner
Dominik,
while comparing the current git with the last release to check
differences, I noticed that the COLR stuff is quite large. IMHO, it
deserves to be moved into a separate file. What do you think? If you
agree, can you do that?
I can imagine to move COLR stuff into `ftcolor.h` so that
> One more screenshot
This looks very nice :-)
Werner
>> > I'm attaching the two patches below, [...]
>>
>> Thanks for applying. I've polished the code a bit; please check.
>
> We do not define FT_LOAD_TARGET_SDF yet, which is necessary for
> FT_LOAD_RENDER to work. It would make sense if it implied
> FT_LOAD_NO_HINTING as the purpose here to hav
>>> You used to release a new version around this time of year. What
>>> are your plans this time around? Are you waiting for some
>>> official specs for COLRv1?
>>
>> Not really for the official specs, but for green light that the
>> COLRv1 stuff is OK to be published as experimental but stable.
Hello Alexei,
your recent t42 change causes memory leaks. If you build the `driver`
program from 'freetype2-testing' without sanitizers and with FreeType
debugging activated, a call to
valgrind --leak-check=full \
--show-leak-kinds=all \
freetype2-testing/fuzzing/build/bin/dr
Sarthak, Anurag,
it seems I've missed to answer this e-mail. Sorry for that.
> [...] here is the proposed UX of the website:
>
> (The artefact is a tarball, when you extract and open the folder,
> you see this):
>
> An index.html file, a folder called regressions.
>
> On opening the index.
> I just wanted to know if it is possible to compile the FreeType
> demos with static linking?
Yes, for example with
cd freetype-demos
meson subprojects update
meson setup --default-library static build
meson compile -C build
Of course, this only links the FreeType library statically i
>> I just wanted to know if it is possible to compile the FreeType
>> demos with static linking?
>
> Yes, for example with
>
> cd freetype-demos
> meson subprojects update
> meson setup --default-library static build
> meson compile -C build
Uh, oh, this doesn't work currently. Workin
> On running "make devel" in freetype source it says something like
> "make: Nothing to be done for 'devel'". So, I presume static linking
> is not working properly right now in autotools ...
Start like the following for FreeType:
git clean -fdx
make devel
make
This is GNU make compilati
>> I just wanted to know if it is possible to compile the FreeType
>> demos with static linking?
>
> Yes, for example with
>
> cd freetype-demos
> meson subprojects update
> meson setup --default-library static build
> meson compile -C build
>
> Of course, this only links the FreeType lib
Meson experts,
please have a look at
https://gitlab.freedesktop.org/freetype/freetype/-/merge_requests/46
Is this the right approach? I'm not completely happy about the
message meson emits, and that the normal case (i.e., logging support
is disabled) is indicated with a red 'NO', which mig
> There are two new warnings from building 2.10.4 on current fedora.
> One is likely from the newer gcc 11:
>
>
> src/base/ftlcdfil.c:360:42: warning:
> argument 2 of type ‘FT_Vector *’ {aka ‘struct FT_Vector_ *’}
> declared as a pointer [-Warray-parameter=]
> 360 |
Hello Nikolaus!
> What message do you mean?
What are you referring to?
> I don't know meson well enough, but a quick skim of the Meson
> offline manual and the one on https://mesonbuild.com show no easy
> option to configure a project "from within".
It seems so. Here I definitely lack the f
Hello Anuj,
> The implementation only supports single channel SDF. So the
> documentation for ` FT_RENDER_MODE_SDF ` is correct. Thanks though,
> the comment might need some editing.
Care to provide a small patch?
Werner
>>> What message do you mean?
>>
>> What are you referring to?
>
> I was stumped by "I'm not completely happy about the message meson
> emits“. Do you mean the red „No“?
Yes, and the message itself, which I admittedly abuse for testing a
local header file. I don't want something dramatic, jus
> Freedesktop.org is down for more than 12 hours now
Yes, and we can't do anything except waiting until the problem has
been fixed. Of course, such things happen during a weekend :-|
Werner
>>> Freedesktop.org is down for more than 12 hours now
>>
>> Yes, and we can't do anything except waiting until the problem has
>> been fixed. Of course, such things happen during a weekend :-|
>
> The admins can be found on #freedesktop on irc.oftc.net, where they
> report the problem has be
> *> Care to provide a small patch?*
>
> Attached below.
Applied (with small corrections), thanks!
Werner
> I would have preferred to use a GitLab merge request, but I keep
> getting a 500 error today when trying to sign up for
> gitlab.freedesktop.org. Use `git am --keep-non-patch` or `git
> mailinfo -b` on these patch emails to keep the `[base]` in the
> subject.
Thanks for your two patches! I've
FreeType 2.11.0 has been released.
It is available from
http://savannah.nongnu.org/download/freetype/
or
http://sourceforge.net/projects/freetype/files/
The latter site also holds older versions of the FreeType library.
See below for the relevant snippet from the CHANGES file.
Enjo
Folks,
for further commits, entries in the `ChangeLog` file are no longer
necessary. Instead, we will auto-generate this file, as is done by
other GNU projects like 'Emacs' or 'coreutils'.
To make that work, I ask to format git commit messages in the same
style that has been used in the last
> It seems "ttdebug" seems to be missing from
> freetype2-demos/meson.build and won't get installed using meson
> build.
Indeed. Thanks for the report, I will take care of this.
> And a 2nd issue. The test suite fails for me due to a missing ttf
> font. Shouldn't it be included in the source
> It seems "ttdebug" seems to be missing from
> freetype2-demos/meson.build and won't get installed using meson
> build.
This should be fixed now in the git repository. Please test.
Werner
Anuj,
now that SDF support is publicly available I think it might be useful
to extend the `freetype2-testing` repository with a fuzzer. Would you
like to have a look to check whether you can implement this?
https://github.com/freetype/freetype2-testing
Werner
Hello Anuj,
> I did check it out and I think simply adding the new render modes to
> the render mode list should be sufficient. [...]
Looks good! Please submit a Pull Request that Armin (and others) can
review.
Note that a major problem will probably be timeouts: Right now it can
happen tha
> I've just submitted a draft MR that brings OT-SVG functionality to
> FreeType. The code added allows client applications to grab the SVG
> document given a glyph ID as well as allows rendering it to a bitmap
> if renderer hooks are plugged-in externally.
Thanks a lot, it looks good to me.
>
>> Looks good! Please submit a Pull Request that Armin (and others)
>> can review.
>
> Done!
Thanks.
> The fuzzer already found a bug in the renderer, I have attached a
> patch (diff.txt) to fix this
> (https://github.com/freetype/freetype2-testing/runs/3213214141). If
> you require a merge
> As you can see in the TODO list in the MR, one of the items is
> having official hooks and documentation on how to create them. I'm
> trying to write them in the repo below. Maybe ultimately we can
> host it inside the FreeType group of repositories.
>
> https://gitlab.freedesktop.org/moazin
>> I had a quick look at the code, and I've immediately found a
>> fundamental problem: You are directly accessing
>> `library->svg_renderer_state`. This is a no-go for applications
>> since `FT_Library` is an opaque pointer that must not be
>> dereferenced.
>>
>> Is it actually necessary that `
> I have added a feature for showing an image diff overlay on hover,
> on the website. Here is a link to the screen record of the latest
> version:
>
> https://drive.google.com/file/d/1KQAmoj68w8WIp4ZloF_dY6SgaBsr_tsb/view?usp=sharing
>
> Please check it out and tell me if you have any feedback
1601 - 1700 of 4490 matches
Mail list logo
